Sell DownloadsWordPress extension · Codepeople
CVE-2015-9348
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 · uneditedThe sell-downloads plugin before 1.0.8 for WordPress has insufficient restrictions on brute-force guessing of purchase IDs.
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 confidenceThe sell-downloads WordPress plugin before version 1.0.8 lacks proper rate limiting, account lockout, or CAPTCHA protections on the purchase ID verification endpoint, allowing remote attackers to systematically brute-force guess valid purchase IDs to access paid content without authorization.
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
Sell DownloadsWordPress extension
< 1.0.8CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 plugin installationCheck if the 'sell-downloads' plugin directory exists in wp-content/plugins/ of the WordPress installationAffected if The plugin directory is present on the server
-
Identify installed versionOpen the main plugin file (sell-downloads.php or similar) in wp-content/plugins/sell-downloads/ and locate the version header comment or version constantAffected if The version number is found to be less than 1.0.8
-
Locate purchase ID endpointSearch plugin PHP files for the purchase ID verification handler, typically containing references to 'purchase_id', 'verify', or 'download' functionalityAffected if A purchase ID verification endpoint is found in the plugin code
-
Verify missing protectionsInspect the purchase ID handler code for absence of rate limiting functions, CAPTCHA calls, or account lockout mechanismsAffected if The endpoint processes purchase IDs without rate limiting, CAPTCHA, or account lockout logic
-
Test endpoint accessibilityIf possible, make a request to the purchase ID verification URL (commonly /?sd_action=verify_purchase or similar) and observe if multiple rapid requests are allowed without restrictionAffected if Multiple rapid requests with different purchase IDs succeed without any throttling or blocking
The environment is affected if the sell-downloads plugin is installed with a version lower than 1.0.8 and the purchase ID verification endpoint is accessible without rate limiting, CAPTCHA, or account lockout protections.
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 data1.0.8
Upgrade the sell-downloads plugin to version 1.0.8 or later which implements proper restrictions on brute-force guessing attempts.
Fix this in Sell Downloads
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9348 — 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-2015-9348 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