InvoicesWordPress extension · Ithemes
CVE-2015-9370
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 · uneditedInvoices Add-on for iThemes Exchange before 1.4.0 for WordPress has XSS via add_query_arg() and remove_query_arg().
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 confidenceInvoices Add-on for iThemes Exchange before version 1.4.0 contains a reflected Cross-Site Scripting (XSS) vulnerability. The plugin uses WordPress add_query_arg() and remove_query_arg() functions to manipulate URL query parameters, but the output is not properly sanitized or escaped before being rendered in HTML pages. This allows attackers to inject malicious JavaScript code through crafted URLs containing malicious payload in query 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
InvoicesWordPress extension
< 1.4.0CVSS 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.0/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.
-
Locate the iThemes Exchange Invoices Add-on pluginNavigate to WordPress admin > Plugins and look for 'Invoices Add-on for iThemes Exchange' or check the plugin directory for the invoices addon filesAffected if The plugin is not installed or not present in the environment
-
Identify the installed version numberIn WordPress admin, go to Plugins > Installed Plugins > click on 'Invoices Add-on for iThemes Exchange' to view the version number in the plugin header, or inspect the main plugin file (usually class-it-exchange-invoices-addon.php) for the 'Version' header commentAffected if The version displayed is lower than 1.4.0
-
Verify the version against affected rangeCompare your identified version to the vulnerable range: any version from 0.x up to and including 1.3.x is affected; version 1.4.0 and later are patchedAffected if The installed version is less than 1.4.0 (e.g., 1.3.9, 1.2.0, 0.5.2)
-
Confirm plugin is activeCheck the Plugins page in WordPress admin to verify the Invoices Add-on is activatedAffected if The plugin is active and the version is below 1.4.0
You are affected if the Invoices Add-on for iThemes Exchange is installed, active, and running a version lower than 1.4.0.
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.4.0
Upgrade to Invoices Add-on for iThemes Exchange version 1.4.0 or later. If immediate patching is not possible, implement output escaping using esc_url(), esc_attr(), or esc_html() on all instances where add_query_arg() and remove_query_arg() output is rendered in HTML.
Fix this in Invoices
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9370 — 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-9370 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