dbcve.org
Menu Bar Cart Icon For WoocommerceWordPress extension · Binarycarpenter

CVE-2023-49855

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 1.49.3 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
Cross-Site Request Forgery (CSRF) vulnerability in BinaryCarpenter Menu Bar Cart Icon For WooCommerce By Binary Carpenter.This issue affects Menu Bar Cart Icon For WooCommerce By Binary Carpenter: from n/a through 1.49.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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the BinaryCarpenter Menu Bar Cart Icon For WooCommerce plugin allows attackers to induce authenticated users to perform unwanted actions (such as modifying cart settings or performing cart operations) via crafted requests. The plugin lacks proper anti-CSRF token validation on its administrative and frontend actions.

MitigationApply vendor patch/upgrade to latest version of the plugin. The fix involves implementing proper anti-CSRF nonce tokens on all state-changing requests and validating the nonce server-side before processing any cart or settings modifications.

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
Menu Bar Cart Icon For WoocommerceWordPress extension
Affected:<= 1.49.3

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. Locate the plugin in WordPress
    Navigate to WordPress admin > Plugins > Installed Plugins and search for 'Binarycarpenter Menu Bar Cart Icon For Woocommerce' or 'Menu Bar Cart Icon'. Confirm the plugin is present and note its activation status.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed version
    In the Plugins list, locate the BinaryCarpenter Menu Bar Cart Icon For Woocommerce plugin and read the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The version number cannot be determined or the plugin file is missing.
  3. Compare version against affected range
    Compare your installed version to the affected range: any version less than or equal to 1.49.3 is within the affected range. If your version is 1.49.3 or lower, you are potentially affected by this CSRF vulnerability.
    Affected if Installed version is <= 1.49.3, indicating the plugin lacks proper anti-CSRF nonce validation.
  4. Inspect for nonce implementation (optional)
    Examine the plugin's PHP files that handle cart operations or settings changes. Look forwp_nonce_field() or wp_nonce_url() calls in forms, and verify_nonce() or check_admin_referer() calls in the corresponding processing code. If these are missing or incomplete, the CSRF protection is absent.
    Affected if State-changing actions (cart operations, settings saves) lack proper nonce verification in the code.

Your environment is affected if the BinaryCarpenter Menu Bar Cart Icon For WooCommerce plugin is active with version 1.49.3 or lower, or if the plugin code shows missing nonce validation on cart or settings actions.

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.

From vendor data
Upgrade available Upgrade to a release after 1.49.3
Interim mitigation

Apply vendor patch/upgrade to latest version of the plugin. The fix involves implementing proper anti-CSRF nonce tokens on all state-changing requests and validating the nonce server-side before processing any cart or settings modifications.

Fix this in Menu Bar Cart Icon For Woocommerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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