CVE-2015-9527
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 Easy Digital Downloads (EDD) Simple Shipping extension for WordPress, as used with EDD 1.8.x before 1.8.7, 1.9.x before 1.9.10, 2.0.x before 2.0.5, 2.1.x before 2.1.11, 2.2.x before 2.2.9, and 2.3.x before 2.3.7, has XSS because add_query_arg is misused.
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 Easy Digital Downloads (EDD) Simple Shipping WordPress extension contains a Cross-Site Scripting (XSS) vulnerability caused by misuse of the add_query_arg function, which fails to properly sanitize URL parameters before output. This allows authenticated attackers with contributor-level or higher permissions to inject malicious JavaScript code that executes in the context of other users' browsers.
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.8, < 1.8.7>= 1.9, < 1.9.10>= 2.0, < 2.0.5>= 2.1, < 2.1.11>= 2.2, < 2.2.9>= 2.3, < 2.3.7all versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify Easy Digital Downloads installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Digital Downloads' by Awesomemotive. Note the version number displayed under the plugin name.Affected if The plugin is installed and its version falls within any of these ranges: >= 1.8 and < 1.8.7; >= 1.9 and < 1.9.10; >= 2.0 and < 2.0.5; >= 2.1 and < 2.1.11; >= 2.2 and < 2.2.9; >= 2.3 and < 2.3.7.
-
Check for Simple Shipping extensionIn WordPress admin, go to Downloads > Settings > Extensions, or check the Plugins list for a plugin named 'Simple Shipping' by 'Easy Digital Downloads' or 'Easydigitaldownloads'.Affected if The Simple Shipping extension is installed and active, regardless of version.
-
Verify user role configurationIn WordPress admin, go to Users > Users and review the roles assigned to each user account. Specifically identify any users with 'Contributor', 'Author', 'Editor', or Administrator roles.Affected if There exists at least one user account with Contributor-level or higher permissions, as this role is required to exploit the vulnerability.
-
Inspect for suspicious URL parameters in admin pagesWhen viewing any EDD admin pages (particularly settings pages under Downloads), examine the browser address bar for any unusual query parameters in the URL. Also check server access logs for requests to /wp-admin/ containing query arguments that may contain script tags or encoded JavaScript.Affected if Any URL parameters passed to add_query_arg functions on EDD admin pages are not properly escaped before output, indicating the vulnerable code is present.
You are affected if Easy Digital Downloads is installed with a version matching the affected ranges AND the Simple Shipping extension is active AND at least one user with Contributor-level or higher access exists in WordPress.
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.8.71.9.102.0.5
Update the EDD Simple Shipping extension to version 1.8.7, 1.9.10, 2.0.5, 2.1.11, 2.2.9, or 2.3.7 or later, which properly escape output when using add_query_arg.
- 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-9527 — 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-9527 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