WoocommerceWordPress extension
CVE-2015-2329
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 · uneditedCross-site scripting (XSS) vulnerability in the WooCommerce plugin before 2.3.6 for WordPress allows remote attackers to inject arbitrary web script or HTML via a crafted order.
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 WooCommerce plugin for WordPress versions before 2.3.6 allows remote attackers to inject arbitrary web script or HTML via a crafted order. This is a stored XSS vulnerability affecting the order processing functionality.
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
WoocommerceWordPress extension
< 2.3.6CVSS 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.
-
Confirm WooCommerce plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for WooCommerce in the list. Note if it is active or inactive.Affected if WooCommerce plugin is present and active in the WordPress installation
-
Identify the installed WooCommerce versionIn WordPress admin, go to Plugins > Installed Plugins, find WooCommerce, and view the version number displayed under the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/woocommerce/woocommerce.php for the Version field.Affected if The installed version is any version before 2.3.6 (e.g., 2.3.5, 2.3.4, 2.3.0, etc.)
-
Verify order processing functionality is accessibleLog in to WordPress admin and navigate to WooCommerce > Orders to confirm the order management functionality is accessible and operational.Affected if The WooCommerce orders feature is accessible, which is required for the stored XSS to be triggered when viewing crafted orders
-
Compare installed version to affected rangeCross-reference the identified WooCommerce version against the vulnerable range: versions strictly less than 2.3.6 are affected. Versions 2.3.6 and later are not affected.Affected if The installed version number is lower than 2.3.6, indicating the environment falls within the vulnerable version range
If WooCommerce is installed with a version number lower than 2.3.6 and the order processing functionality is accessible, the environment is affected by this stored XSS vulnerability in the order processing feature.
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 data2.3.6
Update WooCommerce plugin to version 2.3.6 or later to remediate this vulnerability. Verify order processing functionality after the update.
Fix this in Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2329 — 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-2329 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