Booster For WoocommerceWordPress extension · Booster
CVE-2023-52230
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 · uneditedMissing Authorization vulnerability in Pluggabl LLC Booster Plus for WooCommerce.This issue affects Booster Plus for WooCommerce: from n/a before 7.1.3.
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 confidenceMissing Authorization vulnerability in Booster Plus for WooCommerce allows authenticated users to perform unauthorized actions due to insufficient access controls. The issue is remediated in version 7.1.3 by adding proper capability checks before executing privileged operations.
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.1.3CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Verify Booster Plus for WooCommerce is installedCheck your WordPress plugins directory or access the Plugins page in WordPress admin to confirm Booster Plus for WooCommerce is activeAffected if The plugin is installed and active
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Booster Plus for WooCommerce and note the version number displayedAffected if Version is 7.1.3 or lower (any version up to and including 7.1.3)
-
Confirm WordPress user accounts existNavigate to Users > All Users in WordPress admin to review registered user accountsAffected if Any authenticated user accounts exist in the WordPress installation
-
Review user roles with admin accessCheck the role assignment for each user in the Users panel, noting any users assigned Administrator or elevated rolesAffected if There are users with elevated roles who should not have administrative access
You are affected if Booster Plus for WooCommerce version 7.1.3 or lower is installed and your site has multiple user accounts, particularly if any non-administrator users have unauthorized access to privileged operations.
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 · scopedUpgrade Booster Plus for WooCommerce to version 7.1.3 or later. Additionally, review user role capabilities and audit admin accounts for any unauthorized modifications.
7.1.3
- 1. Log in to the WordPress admin dashboard.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate 'Booster Plus for WooCommerce' in the plugin list.
- 4. If an update is available, click 'Update Now' to update to the latest version.
- 5. Alternatively, download the latest version from the WordPress plugin repository or from the vendor's website.
- 6. After updating, verify the plugin is running version 7.1.3 or later.
- 7. Test key WooCommerce functionality to ensure the update did not break existing features.
Generated from the published advisory — verify against the referenced sources before acting.
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-2023-52230 — 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-2023-52230 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