dbcve.org
Booster Elite WoocommerceWordPress extension · Booster

CVE-2022-4017

HIGH · 8.8 CVSS v3.1 Published 2023-01-23
Fix available
A fix is available. Upgrade to 6.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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
The Booster for WooCommerce WordPress plugin before 6.0.1, Booster Plus for WooCommerce WordPress plugin before 6.0.1, Booster Elite for WooCommerce WordPress plugin before 6.0.1 have either flawed CSRF checks or are missing them completely in numerous places, allowing attackers to make logged in users perform unwanted actions via CSRF attacks

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

Multiple Booster for WooCommerce WordPress plugins (Booster, Booster Plus, Booster Elite) before version 6.0.1 contain flawed or missing CSRF (Cross-Site Request Forgery) protection checks in numerous endpoints. Attackers can craft malicious links or pages that, when visited by authenticated users, cause the user's browser to perform unwanted actions on the vulnerable site without the user's consent.

MitigationUpdate all affected Booster for WooCommerce plugins to version 6.0.1 or later. Additionally, review user actions and consider implementing additional nonce validation and referer checks for sensitive 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 Elite WoocommerceWordPress extension
Affected:< 6.0.1
Booster For WoocommerceWordPress extension
Affected:< 6.0.1
Booster Plus WoocommerceWordPress extension
Affected:< 6.0.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Identify installed Booster plugins
    Check the WordPress plugins directory or admin panel for any installed Booster for WooCommerce plugins (Booster, Booster Plus, Booster Elite)
    Affected if Any of these three plugins appear in the installed plugins list
  2. Check Booster plugin version
    Navigate to Plugins > Installed Plugins in WordPress admin, or inspect the main plugin file (e.g., includes/class-wcj.php) to read the version header
    Affected if The reported version is below 6.0.1 or no version is displayed (indicating an old release)
  3. Verify plugin status
    Confirm whether the vulnerable plugin is active on the site
    Affected if The plugin is active and version is below 6.0.1

The environment is affected if any Booster for WooCommerce plugin (Booster, Booster Plus, or Booster Elite) is installed and active with a version number less than 6.0.1.

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 6.0.1 or later
Fixed in 6.0.1
Interim mitigation

Update all affected Booster for WooCommerce plugins to version 6.0.1 or later. Additionally, review user actions and consider implementing additional nonce validation and referer checks for sensitive operations.

Recommended fix High confidence

6.0.1

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Booster Elite WooCommerce', 'Booster for WooCommerce', or 'Booster Plus WooCommerce' plugin
  4. Check the current version installed
  5. If version is below 6.0.1, click 'Update Now' to upgrade to version 6.0.1
  6. Alternatively, download version 6.0.1 or later from a trusted source and upload via Plugins > Add New > Upload Plugin
  7. After upgrade, verify the new version is 6.0.1 or higher
  8. Test critical 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 Elite Woocommerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

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