dbcve.org
Booster For WoocommerceWordPress extension · Booster

CVE-2024-29760

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 7.1.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Pluggabl LLC Booster for WooCommerce allows Reflected XSS.This issue affects Booster for WooCommerce: from n/a through 7.1.7.

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 confidence

A reflected Cross-site Scripting (XSS) vulnerability in the Booster for WooCommerce plugin allows unauthenticated attackers to inject malicious JavaScript code through unsanitized user input that gets reflected in web page responses without proper output encoding.

MitigationUpgrade Booster for WooCommerce to the latest patched version that implements proper input sanitization and output encoding. As an interim measure, deploy a WAF rule to block XSS attack patterns in query parameters.

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
Affected:< 7.1.8

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Booster for WooCommerce is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Booster for WooCommerce' in the list of active plugins.
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In the Plugins list, click on 'Booster for WooCommerce' to view the plugin details, or check the plugin file header in wp-content/plugins/booster-for-woocommerce/booster-for-woocommerce.php for the 'Version' constant.
    Affected if The version displayed is a number less than 7.1.8 (for example, 7.1.7, 7.1.6, etc.)
  3. Verify the vulnerability is reachable
    Since this is a reflected XSS, test any page on the site that accepts user input via URL parameters (such as search fields or query parameters). Attempt to inject a harmless test string like <script>alert(1)</script> into a URL parameter and observe if it is reflected unescaped in the response.
    Affected if The test string appears literally in the HTML output without being HTML-encoded (characters like < and > display as-is rather than as &lt; and &gt;)

You are affected if Booster for WooCommerce is installed with a version number lower than 7.1.8 and any URL parameter on your site reflects user input without HTML encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.1.8 or later
Fixed in 7.1.8
Interim mitigation

Upgrade Booster for WooCommerce to the latest patched version that implements proper input sanitization and output encoding. As an interim measure, deploy a WAF rule to block XSS attack patterns in query parameters.

Recommended fix Moderate confidence

7.1.8

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find 'Booster for WooCommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 7.1.8
  5. 5. Alternatively, download version 7.1.8 from the official WordPress plugin repository or your purchased source
  6. 6. Deactivate and delete the current version, then upload and install version 7.1.8
  7. 7. After upgrading, clear any site caches and test the plugin functionality
  8. 8. Verify the XSS vulnerability is resolved by testing the affected input fields

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Booster For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29760 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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