dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64222

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Missing Authorization vulnerability in FantasticPlugins WooCommerce Recover Abandoned Cart rac allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooCommerce Recover Abandoned Cart: from n/a through <= 24.6.0.

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

The WooCommerce Recover Abandoned Cart plugin (versions up to 24.6.0) by FantasticPlugins contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthenticated or unauthorized access to sensitive abandoned cart data or administrative functions due to improper capability checks on specific endpoints or actions.

MitigationUpdate the WooCommerce Recover Abandoned Cart plugin to the latest version when available, or temporarily restrict access to the plugin's admin interfaces via web server configuration until a patch is applied.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, find 'WooCommerce Recover Abandoned Cart' by FantasticPlugins, and read the version number displayed. Alternatively, access the plugin's main PHP file via FTP or file manager (typically in wp-content/plugins/recover-abandoned-cart or similar path) and inspect the plugin header for the 'Version' field.
    Affected if The displayed version is 24.6.0 or any earlier version number (e.g., 24.5.0, 24.0.0, 1.0.0).
  2. Identify plugin directory name
    List the contents of the wp-content/plugins directory and identify the exact folder name used by the WooCommerce Recover Abandoned Cart plugin (common patterns include 'recover-abandoned-cart', 'woocommerce-recover-abandoned-cart', or 'fantasticplugins-recover-abandoned-cart').
    Affected if The plugin folder exists and contains the vulnerable plugin files.
  3. Verify admin endpoint exposure
    If the site uses a REST API, attempt to access common plugin-related REST routes (such as /wp-json/recover-abandoned-cart/v1/ or similar endpoints) without providing authentication credentials. Check if the server returns cart data or administrative responses instead of a 401/403 error.
    Affected if Requests to plugin-specific REST API endpoints return successful data responses without requiring valid WordPress authentication.
  4. Test admin-ajax accessibility
    Inspect page source or network traffic while visiting the plugin admin pages to identify admin-ajax actions (look for 'action' parameters in POST requests to /wp-admin/admin-ajax.php). Then, send a direct POST request to admin-ajax.php with the identified action parameter but without valid authentication cookies or with a low-privilege user account.
    Affected if The plugin's admin-ajax actions return sensitive abandoned cart data or perform administrative operations without verifying user capabilities.
  5. Review capability checks in plugin code
    Download the main plugin PHP file and search for function calls that verify user capabilities, such as 'current_user_can', 'check_admin_referer', or 'wp_verify_nonce'. Compare the placement and coverage of these checks against sensitive functions that handle cart data retrieval or administrative actions.
    Affected if Critical functions handling abandoned cart data or administrative operations lack proper capability checks or contain checks that can be bypassed.

You are affected if the WooCommerce Recover Abandoned Cart plugin version installed is 24.6.0 or earlier, and unauthenticated or unauthorized users can access abandoned cart data or administrative functions through exposed endpoints.

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 WooCommerce Recover Abandoned Cart plugin to the latest version when available, or temporarily restrict access to the plugin's admin interfaces via web server configuration until a patch is applied.

Have this fixed 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 help mitigating

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-2025-64222 — 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-2025-64222 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