dbcve.org
Booster Elite For WoocommerceWordPress extension · Booster

CVE-2022-4227

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-26
Fix available
A fix is available. Upgrade to 5.6.3 / 6.0.0 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
The Booster for WooCommerce WordPress plugin before 5.6.3, Booster Plus for WooCommerce WordPress plugin before 6.0.0, Booster Elite for WooCommerce WordPress plugin before 6.0.0 do not escape some URLs and parameters before outputting them back in attributes, leading to Reflected Cross-Site Scripting

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 plugin (free, Plus, and Elite versions) fails to properly escape URLs and parameters before outputting them in HTML attributes, creating a reflected Cross-Site Scripting (XSS) vulnerability. An attacker can craft malicious URLs containing JavaScript payload in parameters that get reflected unescaped into the page, executing in victim browsers.

MitigationUpgrade to Booster for WooCommerce 5.6.3 or higher (free), or 6.0.0+ for Plus/Elite versions. As an interim measure, implement URL parameter validation and output encoding using WordPress escaping functions like esc_url() and esc_attr() before rendering any user-supplied data.

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 For WoocommerceWordPress extension
Affected:< 6.0.0
Booster For WoocommerceWordPress extension
Affected:< 5.6.3
Booster Plus For WoocommerceWordPress extension
Affected:< 6.0.0

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. Locate the installed Booster for WooCommerce plugin
    In WordPress admin, go to Plugins > Installed Plugins and find 'Booster Elite for WooCommerce', 'Booster Plus for WooCommerce', or 'Booster for WooCommerce'. Note which edition is installed.
    Affected if Any edition of Booster for WooCommerce is installed
  2. Identify the installed version number
    In the plugins list, view the plugin details to see the version number (e.g., displayed next to the plugin name).
    Affected if Version is less than 5.6.3 for free version, or less than 6.0.0 for Plus/Elite versions
  3. Compare version against vulnerable ranges
    Check if the installed version falls into: Booster (free) < 5.6.3, Booster Plus < 6.0.0, or Booster Elite < 6.0.0
    Affected if Installed version is below the safe threshold for that edition
  4. Inspect for reflected URL parameters in output
    If running an affected version, examine page source or use browser dev tools to see if URL query parameters (e.g., ?param=value) are reflected in HTML without encoding
    Affected if URL parameters appear unescaped in HTML output (visible script tags or raw parameter values in attributes)

You are affected if you have Booster for WooCommerce installed with a version below 5.6.3 (free) or below 6.0.0 (Plus/Elite) and are outputting URL parameters in pages without proper escaping.

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 5.6.3 / 6.0.0 or later
Fixed in 5.6.36.0.0
Interim mitigation

Upgrade to Booster for WooCommerce 5.6.3 or higher (free), or 6.0.0+ for Plus/Elite versions. As an interim measure, implement URL parameter validation and output encoding using WordPress escaping functions like esc_url() and esc_attr() before rendering any user-supplied data.

Recommended fix High confidence

Booster for WooCommerce: 5.6.3 or later | Booster Plus for WooCommerce: 6.0.0 or later | Booster Elite for WooCommerce: 6.0.0 or later

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Booster for WooCommerce (or Booster Plus/Elite) in the plugin list
  4. Click 'Update now' on the plugin to install the latest patched version
  5. Verify the update was successful by checking the plugin version matches or exceeds the fixed release (5.6.3 for Booster, 6.0.0 for Booster Plus/Elite)

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

Fix this in Booster Elite For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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