CVE-2013-2697
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site request forgery (CSRF) vulnerability in the WP-DownloadManager plugin before 1.61 for WordPress allows remote attackers to hijack the authentication of arbitrary users for requests that insert XSS sequences.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCSRF vulnerability in WP-DownloadManager plugin for WordPress allows remote attackers to hijack authenticated users' sessions and inject arbitrary XSS sequences through crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.60= 1.00= 1.30= 1.31= 1.40= 1.50CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm WP-DownloadManager plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP-DownloadManager' in the list of active plugins.Affected if The plugin appears in the installed plugins list and is activated
-
Identify installed version of WP-DownloadManagerIn WordPress admin, go to Plugins > Installed Plugins. Find WP-DownloadManager and locate the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file (wp-downloadmanager.php) for the 'Version' header comment.Affected if The displayed version matches any of: 1.00, 1.30, 1.31, 1.40, 1.50, or any version <= 1.60
-
Verify plugin handles file download requestsInspect whether the plugin's download functionality is accessible on the site. Visit a page where download links managed by the plugin exist, or check if the wp-downloadmanager endpoint is reachable.Affected if The plugin's download functionality is active and accessible to authenticated users
-
Check for CSRF protection in plugin formsReview the plugin's source code (wp-downloadmanager.php) for presence of nonces or CSRF tokens in form handling functions, particularly those processing user-supplied input for file downloads or XSS-susceptible fields.Affected if No CSRF tokens are implemented in form submissions or admin actions within the plugin
The environment is affected if WP-DownloadManager is installed with any version from 1.00 to 1.60 inclusive and the plugin is active, as this version range lacks CSRF protection allowing XSS injection via hijacked authenticated sessions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate WP-DownloadManager plugin to version 1.61 or later to remediate the CSRF vulnerability that enables XSS injection.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2697 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data