dbcve.org
CartbountyWordPress extension · Majas Lapu Izstrade

CVE-2024-47634

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to 8.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Streamline CartBounty – Save and recover abandoned carts for WooCommerce woo-save-abandoned-carts allows Cross Site Request Forgery.This issue affects CartBounty – Save and recover abandoned carts for WooCommerce: from n/a through <= 8.2.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the CartBounty WordPress plugin allows attackers to trick authenticated users into performing unintended actions (such as manipulating abandoned cart data or modifying settings) by leveraging the absence of proper anti-CSRF token validation on sensitive form submissions and AJAX actions.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing forms and AJAX endpoints, verify nonce validity server-side before processing requests, and consider adding SameSite cookie attributes and Origin/Referer header validation for defense-in-depth.

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
CartbountyWordPress extension
Affected:< 8.2.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 CartBounty plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate CartBounty (Majas Lapu Izstrade), and read the version number displayed
    Affected if The installed version is lower than 8.2.1
  2. Confirm CartBounty is active
    In the same plugins list, verify that CartBounty shows as 'Active' rather than 'Inactive' or 'Not Installed'
    Affected if The plugin is active and version is below 8.2.1
  3. Determine if abandoned cart features are in use
    Check if CartBounty abandoned cart tracking is enabled and if there are saved abandoned cart records in the WordPress database or admin interface
    Affected if Abandoned cart functionality is active with stored cart data and the plugin version is vulnerable
  4. Check for state-changing admin actions
    Review CartBounty settings pages for any forms that modify plugin configuration, abandoned cart data, or export functions
    Affected if Any settings or data manipulation forms exist and the plugin version is below 8.2.1
  5. Inspect AJAX endpoints for nonce validation
    If code access is available, examine CartBounty PHP files for admin-ajax.php handlers and verify that wp_verify_nonce or check_ajax_referer is called before processing state-changing requests
    Affected if AJAX action handlers lack nonce verification and the plugin version is vulnerable

You are affected if CartBounty (Majas Lapu Izstrade) is active at a version lower than 8.2.1 and exposes forms or AJAX endpoints that handle abandoned cart data or plugin settings.

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

Implement WordPress nonces (anti-CSRF tokens) on all state-changing forms and AJAX endpoints, verify nonce validity server-side before processing requests, and consider adding SameSite cookie attributes and Origin/Referer header validation for defense-in-depth.

Recommended fix High confidence

CartBounty version 8.2.1 or latest available version

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'CartBounty – Save and recover abandoned carts for WooCommerce'
  4. Click 'Update now' to update to the latest version (8.2.1 or newer)
  5. Verify the plugin version after update confirms 8.2.1 or later

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

Fix this in Cartbounty 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 the upgrade done

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-47634 — 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-47634 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