CVE-2015-9516
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) Invoices 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 · moderate confidenceThe Easy Digital Downloads (EDD) Invoices extension for WordPress has a Cross-Site Scripting (XSS) vulnerability due to misuse of the WordPress add_query_arg function. This function only constructs URLs and does not sanitize output; when the result is echoed without proper escaping (using functions like esc_attr or esc_url), malicious scripts can be injected via URL parameters.
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.
-
Verify Easy Digital Downloads plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Digital Downloads' or check the file /wp-content/plugins/easy-digital-downloads/readme.txt for the version numberAffected if The plugin is installed and the version falls within one of the affected ranges: >=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, or >=2.3 <2.3.7
-
Verify EDD Invoices extension is installedCheck /wp-content/plugins/edd-invoices/ directory exists, or look for 'EDD Invoices' in Plugins listAffected if The EDD Invoices extension directory exists in the plugins folder (all versions are affected)
-
Check if the Invoices extension is activeIn WordPress admin > Plugins, verify if EDD Invoices is activatedAffected if The Invoices extension is active and the main EDD version is within affected ranges
-
Identify vulnerable add_query_arg usage in EDD Invoices codeSearch files in /wp-content/plugins/edd-invoices/ for add_query_arg calls that are echoed or printed directly without esc_attr() or esc_url() wrapping, for example: echo add_query_arg(...) or print add_query_arg(...)Affected if Code contains add_query_arg output without proper escaping functions like esc_attr(), esc_url(), or esc_html()
You are affected if Easy Digital Downloads (any version from the affected ranges) AND the EDD Invoices extension are both installed and active, with vulnerable add_query_arg usage present in the code.
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 Invoices extension to the patched versions (1.8.7, 1.9.10, 2.0.5, 2.1.11, 2.2.9, or 2.3.7 or later) and ensure all uses of add_query_arg in custom code properly escape output using esc_attr() or esc_url() before rendering.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9516 — 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-9516 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