dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-37202

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 BinaryCarpenter Ultimate Custom Add To Cart Button (Ajax) For WooCommerce by Binary Carpenter custom-add-to-cart-button-for-woocommerce.This issue affects Ultimate Custom Add To Cart Button (Ajax) For WooCommerce by Binary Carpenter: from n/a through <= 1.222.17.

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 the Ultimate Custom Add To Cart Button plugin for WooCommerce allows unauthenticated or unauthorized users to perform certain actions that should require proper authentication and permission checks. The exact endpoints or functions affected are not specified in the available description.

MitigationUpdate the plugin to a version beyond 1.222.17 to receive the vendor's authorization fix, or disable the plugin until a patched version is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 WooCommerce is installed
    Check your WordPress plugins page or inspect the wp-content/plugins directory for WooCommerce
    Affected if WooCommerce is not installed - this is a WooCommerce-specific plugin
  2. Locate the Ultimate Custom Add To Cart Button plugin
    Check your WordPress plugins admin page under WooCommerce extensions, or look for a folder named 'ultimate-custom-add-to-cart-button' in wp-content/plugins
    Affected if The plugin is not found - you are not affected
  3. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the Ultimate Custom Add To Cart Button plugin, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if Cannot determine version - manual code review may be needed to confirm presence of authorization checks
  4. Compare version against affected range
    The vendor fix was released for versions beyond 1.222.17. Compare your installed version number to this threshold
    Affected if Your installed version is 1.222.17 or lower - you are running a vulnerable version
  5. Confirm the plugin is active
    In WordPress admin, verify the plugin status shows as 'Active' under Plugins > Installed Plugins
    Affected if The plugin is inactive - the authorization flaw cannot be exploited in your environment

You are affected if WooCommerce is installed with the Ultimate Custom Add To Cart Button plugin active at version 1.222.17 or lower.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 1.222.17 to receive the vendor's authorization fix, or disable the plugin until a patched version is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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