Manual PurchasesWordPress extension · Ithemes
CVE-2015-9371
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 · uneditedManual Purchases Add-on for iThemes Exchange before 1.1.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 · high confidenceThe Manual Purchases Add-on for iThemes Exchange before version 1.1.0 contains a Cross-Site Scripting (XSS) vulnerability caused by improper use of WordPress functions add_query_arg() and remove_query_arg(). These URL manipulation functions were not properly sanitized before being output, allowing attackers to inject malicious scripts via crafted URLs.
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
Manual PurchasesWordPress extension
< 1.1.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 Manual Purchases Add-on plugin filesIn your WordPress installation, navigate to wp-content/plugins and look for a folder named 'manual-purchases' or similar naming related to iThemes Exchange manual purchases functionalityAffected if The plugin folder exists in your plugins directory
-
Identify the installed versionOpen the main plugin PHP file (usually named index.php or manual-purchases.php) and look for the version comment or header that specifies the plugin versionAffected if The version number found is below 1.1.0 (for example, 1.0.9, 1.0.8, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the Manual Purchases Add-on is activatedAffected if The plugin is active and the version is below 1.1.0
-
Check for vulnerable URL handling code (optional confirmation)Search the plugin PHP files for usage of add_query_arg() or remove_query_arg() functions that output to the browser without esc_url() or esc_attr() sanitizationAffected if The plugin code contains unsanitized output of these URL functions
You are affected if the Manual Purchases Add-on for iThemes Exchange is installed and active with a version number lower than 1.1.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.1.0
Update the Manual Purchases Add-on for iThemes Exchange to version 1.1.0 or later to include the security patch that properly sanitizes query argument output.
Fix this in Manual Purchases
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9371 — 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-9371 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