StripeWordPress extension · Ithemes
CVE-2015-9374
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 · uneditedStripe Add-on for iThemes Exchange before 1.2.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 confidenceCross-site scripting (XSS) vulnerability in the Stripe Add-on for iThemes Exchange plugin for WordPress. The vulnerability stems from improper use of add_query_arg() and remove_query_arg() functions, which generate URL query parameters without sanitizing output before rendering in HTML contexts.
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
StripeWordPress extension
< 1.2.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 Stripe pluginNavigate to your WordPress wp-content/plugins directory and look for a folder named 'exchange-addon-stripe' or similar. In the WordPress admin, go to Plugins > Installed Plugins and locate 'Stripe Add-on for iThemes Exchange' or 'iThemes Exchange Stripe'.Affected if The plugin folder or listing is found in your WordPress installation
-
Find the installed version numberOpen the main plugin PHP file (usually named something like 'exchange-addon-stripe.php' or 'index.php' inside the plugin folder) and look at the plugin header comment which contains 'Version: x.x.x'. Alternatively, check the readme.txt file in the plugin folder for the version number.Affected if A version number is displayed in the plugin header or readme.txt
-
Compare version to affected rangeCompare the version you found to 1.2.0. Any version number less than 1.2.0 (such as 1.1.9, 1.1.0, 1.0.5, etc.) falls within the affected range.Affected if The installed version is less than 1.2.0 (for example: 1.1.9, 1.0.0, or any 1.x.x version below 1.2.0)
-
Verify the vulnerable function usage existsOpen the main plugin PHP file and search for occurrences of 'add_query_arg' or 'remove_query_arg'. Check if these functions are used to build URLs that are later output to HTML without being passed through escaping functions like esc_url(), esc_attr(), or esc_html().Affected if The code contains add_query_arg() or remove_query_arg() calls whose output is rendered in HTML pages without proper sanitization
You are affected if the Stripe Add-on for iThemes Exchange plugin is installed with any version below 1.2.0 and the vulnerable add_query_arg/remove_query_arg functions are used without output escaping.
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.2.0
Update Stripe Add-on for iThemes Exchange to version 1.2.0 or later to obtain the patched code that properly escapes query argument output.
Fix this in Stripe
Scoped from the published advisory
- 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-2015-9374 — 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-9374 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