Booster For WoocommerceWordPress extension · Booster
CVE-2018-20966
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 woocommerce-jetpack plugin before 3.8.0 for WordPress has XSS in the Products Per Page feature.
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 confidenceThe woocommerce-jetpack WordPress plugin before version 3.8.0 contains a stored Cross-Site Scripting (XSS) vulnerability in its Products Per Page feature. This allows authenticated attackers to inject malicious JavaScript into the plugin settings that executes when accessed by other users viewing the affected admin 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
Booster For WoocommerceWordPress extension
< 3.8.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.
-
Identify installed plugin versionNavigate to WordPress admin Plugins page and locate 'Booster Booster For WooCommerce' (formerly woocommerce-jetpack), or check the plugin files for a version file or header comment containing the version numberAffected if The installed version is below 3.8.0
-
Confirm Products Per Page feature is enabledAccess the plugin settings in WordPress admin under Booster > Products > Products Per Page, or inspect the WordPress database options table for 'wcj_products_per_page_enabled' or similar settingAffected if The Products Per Page feature is enabled and the plugin version is vulnerable
-
Inspect Products Per Page setting values for XSS payloadsView the Products Per Page setting value in the plugin admin panel, or query the wp_options table for keys related to 'wcj_products_per_page' to examine stored valuesAffected if The stored setting value contains unexpected HTML, script tags, or JavaScript code that was not entered by an administrator
A user is affected if they have installed Booster For WooCommerce (woocommerce-jetpack) version below 3.8.0 and the Products Per Page feature is enabled with potentially malicious content stored in its settings.
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.0
Update the woocommerce-jetpack plugin to version 3.8.0 or later to patch the XSS vulnerability. Alternatively, restrict administrative access to trusted users and consider using a Web Application Firewall until the update can be applied.
Fix this in Booster For Woocommerce
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-2018-20966 — 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-2018-20966 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