Booster For WoocommerceWordPress extension · Booster
CVE-2025-64196
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Pluggabl Booster for WooCommerce woocommerce-jetpack allows Reflected XSS.This issue affects Booster for WooCommerce: from n/a through <= 7.2.5.
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 confidenceReflected XSS vulnerability in the Booster for WooCommerce plugin (woocommerce-jetpack) allows attackers to inject malicious scripts through unsanitized user input that gets reflected in web pages 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
Booster For WoocommerceWordPress extension
< 7.2.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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 Booster for WooCommerce plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Booster for WooCommerce' or 'woocommerce-jetpack' in the list of active plugins.Affected if Plugin named 'Booster for WooCommerce' or 'woocommerce-jetpack' appears in the installed plugins list
-
Locate the installed plugin version numberIn the WordPress admin plugins list, click on the plugin name or hover over it to reveal the version information. Alternatively, check the plugin header in the main plugin file: /wp-content/plugins/woocommerce-jetpack/woocommerce-jetpack.phpAffected if Version number is displayed and is readable
-
Compare installed version against affected rangeCompare the identified version number to the affected range: versions prior to 7.2.6 are vulnerable. For example, versions like 7.2.5, 7.2.0, 6.9.3, etc. all fall within the affected range.Affected if Installed version is lower than 7.2.6 (e.g., 7.2.5, 7.1.0, 6.9.3, etc.)
-
Confirm the plugin is actively processing user inputReview plugin settings in WooCommerce > Booster. The reflected XSS vulnerability exists in any feature that accepts user input and reflects it back without output encoding. Test by entering a simple test string like '<script>alert(1)</script>' in various Booster module input fields and checking if it executes or appears unescaped in the output.Affected if User-supplied input appears reflected in page output without HTML encoding or the test script tag renders as plain text rather than being encoded
User is affected if the Booster for WooCommerce plugin is installed with any version lower than 7.2.6 and has input fields that reflect user data unescaped in the page output.
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.
dbcve · scoped7.2.6
Apply available security patches for Booster for WooCommerce; upgrade to version 7.2.6 or later once released, and implement Web Application Firewall rules as interim protection.
7.2.6
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Booster for WooCommerce' (woocommerce-jetpack) in the plugin list
- Click 'Update Now' to upgrade to the latest version
- Verify the installed version is 7.2.6 or later
- Clear any caching layers if applicable
- Test the affected functionality to confirm the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Booster For Woocommerce
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64196 — 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-2025-64196 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