dbcve.org
Booster For WoocommerceWordPress extension · Booster

CVE-2023-52232

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 7.1.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Missing Authorization vulnerability in Pluggabl LLC Booster Plus for WooCommerce.This issue affects Booster Plus for WooCommerce: from n/a before 7.1.2.

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

Missing Authorization vulnerability in Booster Plus for WooCommerce allows authenticated users to perform actions without proper capability checks. This could enable unauthorized access to administrative functions or data within the WooCommerce environment.

MitigationUpgrade to Booster Plus for WooCommerce version 7.1.2 or later which includes proper authorization checks. If immediate upgrade is not possible, restrict administrative access and monitor for suspicious user activity.

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.2

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Booster Plus for WooCommerce is installed
    Navigate to WordPress Admin > Plugins and look for 'Booster Plus for WooCommerce' in the installed plugins list, or check the file system at wp-content/plugins/booster-plus-for-woocommerce/ for the main plugin file
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress Admin > Plugins, click on the plugin name to view its details, or open the main plugin file (e.g., booster-plus-for-woocommerce.php) and look for the 'Version' header in the plugin comment block
    Affected if The version number displayed is less than 7.1.2 (e.g., 7.1.1, 7.0.9, etc.)
  3. Check for non-administrative user accounts
    In WordPress Admin > Users, review the list of registered users. Click on individual user profiles to see their assigned roles
    Affected if There are user accounts with roles other than Administrator (e.g., Editor, Author, Subscriber, or custom roles) present in the system
  4. Verify user role capabilities are not properly restricted
    In WordPress Admin > Booster Plus > Users & Roles (if accessible), check if any non-administrative roles have been granted elevated permissions or access to WooCommerce settings
    Affected if Non-administrator users have access to Booster Plus settings or WooCommerce administrative functions that should require Administrator privileges

A user is affected if Booster Plus for WooCommerce version less than 7.1.2 is installed and there are non-administrative user accounts present in the WordPress environment that could potentially access unauthorized functions.

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.2 or later
Fixed in 7.1.2
Interim mitigation

Upgrade to Booster Plus for WooCommerce version 7.1.2 or later which includes proper authorization checks. If immediate upgrade is not possible, restrict administrative access and monitor for suspicious user activity.

Recommended fix High confidence

7.1.2

  1. 1. Update Booster For WooCommerce plugin to version 7.1.2 or later through the WordPress admin dashboard (Plugins > Updates or check for updates)
  2. 2. Alternatively, download version 7.1.2 or newer from the WordPress plugin repository or official source and upload/install via Plugins > Add New > Upload Plugin
  3. 3. After update, verify the plugin version shows 7.1.2 or higher in the installed plugins list

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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