Import All Pages\, Post Types\, Products\, Orders\, And Users As Xml \& CsvWordPress extension · Smackcoders
CVE-2015-9306
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 wp-ultimate-csv-importer plugin before 3.8.1 for WordPress has XSS.
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 confidenceCross-Site Scripting (XSS) vulnerability in the wp-ultimate-csv-importer WordPress plugin versions prior to 3.8.1. An unauthenticated attacker can inject malicious JavaScript code through plugin parameters that gets executed in the context of a victim's browser when viewing affected pages.
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
Import All Pages\, Post Types\, Products\, Orders\, And Users As Xml \& CsvWordPress extension
< 3.8.1CVSS 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.
-
Verify plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Import All Pages, Post Types, Products, Orders, And Users As Xml & Csv' or 'wp-ultimate-csv-importer'. Alternatively, check the /wp-content/plugins/ directory for the wp-ultimate-csv-importer folder.Affected if The plugin folder exists in the WordPress plugins directory.
-
Check installed versionIn the Plugins list, locate the plugin and view the version number displayed under the plugin name. Compare this version to 3.8.1.Affected if The installed version is lower than 3.8.1.
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the plugin status shows as 'Active'.Affected if The plugin is currently active and running.
-
Check exposure to unauthenticated accessThe vulnerability is exploitable by unauthenticated attackers. If the WordPress site allows public access and the plugin handles parameters via HTTP GET or POST requests, the attack surface exists.Affected if The site is publicly accessible and the plugin handles user-supplied parameters without proper sanitization.
A user is affected if the wp-ultimate-csv-importer plugin is installed with a version lower than 3.8.1 and is active on a publicly accessible WordPress site.
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 data3.8.1
Update wp-ultimate-csv-importer to version 3.8.1 or later. If patching is not immediately possible, disable the plugin until the update can be applied.
Fix this in Import All Pages\, Post Types\, Products\, Orders\, And Users As Xml \& Csv
Scoped from the published advisory
- 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-9306 — 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-9306 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