Wp All ImportWordPress extension · Soflyy
CVE-2015-9329
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-all-import plugin before 3.2.5 for WordPress has reflected 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 · moderate confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in the wp-all-import WordPress plugin before version 3.2.5. The vulnerability allows attackers to inject malicious JavaScript or HTML code through unsanitized user input that gets reflected back in the application's HTTP response without proper output encoding.
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
Wp All ImportWordPress extension
< 3.2.5CVSS 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 the installed wp-all-import plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins, locate 'WP All Import', and check the version number displayed beneath the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/wp-all-import/readme.txt or the main plugin PHP file to find the Version field.Affected if The displayed version number is lower than 3.2.5 (for example, 3.2.4, 3.2.0, or any version below 3.2.5).
-
Confirm the plugin is active and accessibleCheck if the wp-all-import plugin is listed as 'Active' in the WordPress Plugins admin page. Also verify that any public-facing pages or admin pages that use the plugin are accessible.Affected if The plugin is active and the version is below 3.2.5, making the vulnerable code load and execute.
-
Identify plugin endpoints handling user inputInspect the plugin's PHP files in /wp-content/plugins/wp-all-import/ for functions that process request parameters (such as $_GET, $_POST, or $_REQUEST) and directly output them into HTML without encoding. Search for patterns like 'echo $_REQUEST' or 'echo $_GET' within the plugin directory.Affected if The plugin code contains unsanitized user input reflection logic and the version is below 3.2.5, indicating the vulnerability is present.
You are affected if the wp-all-import plugin version installed in your WordPress environment is below 3.2.5 and the plugin is active.
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.2.5
Update the wp-all-import plugin to version 3.2.5 or later, which contains the fix for this reflected XSS vulnerability. As a temporary measure, disable the plugin until an update can be applied.
Fix this in Wp All Import
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-9329 — 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-9329 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