dbcve.org
Booster For WoocommerceWordPress extension · Booster

CVE-2024-1534

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 7.1.8 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Booster for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in all versions up to, and including, 7.1.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Booster for WooCommerce WordPress plugin fails to properly sanitize and escape user-supplied attributes in its shortcode functionality. Authenticated attackers with contributor-level permissions or higher can inject malicious JavaScript code through shortcode attributes that gets stored in the database and executed when other users view affected pages.

MitigationUpdate the plugin to version 7.1.8 or later which contains the fix. In the meantime, review shortcode implementations to add proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) for all user-supplied attributes.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify plugin version
    Access WordPress admin > Plugins > Installed Plugins and locate 'Booster for WooCommerce', or run: `wp plugin list --name=booster-for-woocommerce` via WP-CLI
    Affected if The installed version is below 7.1.8 (e.g., 7.1.7, 7.1.0, etc.) or the version field is empty/unavailable indicating an unpatched install
  2. Identify active shortcodes
    Search post content for shortcode tags starting with 'wcj_' (the plugin prefix), for example: `[wcj_price_add_to_cart]`, `[wcj_wholesale_price]`, `[wcj_total_sales]`. Use WP-CLI: `wp db query "SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%[wcj_%'"`
    Affected if Any Booster shortcodes are present in posts, pages, or widget content and the plugin version is below 7.1.8
  3. Check user roles with shortcode injection capability
    Navigate to WordPress admin > Users, or run: `wp user list --role=contributor` and `wp user list --role=author` and `wp user list --role=editor` and `wp user list --role=administrator`
    Affected if One or more users with Contributor, Author, Editor, or Administrator roles exist AND the plugin version is below 7.1.8 with active Booster shortcodes in content

Your environment is affected if Booster for WooCommerce version is below 7.1.8 AND you have Booster shortcodes deployed on your site AND you have users with contributor-level permissions or higher who could inject malicious shortcode attributes.

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

Update the plugin to version 7.1.8 or later which contains the fix. In the meantime, review shortcode implementations to add proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) for all user-supplied attributes.

Recommended fix High confidence

Booster for WooCommerce version 7.1.8

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Booster for WooCommerce' in the plugin list
  4. Click 'Update now' if an update is available, or click 'Check for updates' first if needed
  5. Confirm the update to version 7.1.8
  6. Verify the update was successful by checking the plugin version

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1534 — 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-1534 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