dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-0956

HIGH · 8.1 CVSS v3.1 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
The WooCommerce Recover Abandoned Cart plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 24.4.0 via deserialization of untrusted input from the 'raccookie_guest_email' cookie. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 WooCommerce Recover Abandoned Cart plugin for WordPress versions up to 24.4.0 is vulnerable to PHP Object Injection via deserialization of untrusted data from the 'raccookie_guest_email' cookie. Unauthenticated attackers can inject PHP objects, but exploitation requires a POP chain to be present from another installed plugin or theme to achieve meaningful impact such as arbitrary file deletion, data retrieval, or code execution.

MitigationUpdate the plugin to a version beyond 24.4.0 once available, and audit the WordPress installation for other plugins or themes that may contain exploitable POP chains.

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

CVSS:3.1/AV:N/AC:H/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. Verify if WooCommerce Recover Abandoned Cart plugin is installed
    Check the WordPress plugin directory for 'woocommerce-recover-abandoned-cart' or 'rac' folder, or query the wp_plugins table for plugin slug containing 'recover-abandoned-cart'
    Affected if Plugin is not installed means not affected
  2. Determine installed plugin version
    Read the main plugin file header (e.g., woocommerce-recover-abandoned-cart.php) for the 'Version' tag, or query wp_options for option_name='active_plugins' and check plugin file headers
    Affected if Version is 24.4.0 or lower means the plugin contains the vulnerable deserialization code
  3. Verify cookie processing is active
    Check if the site processes the 'raccookie_guest_email' cookie by reviewing plugin code for unserialize() calls on $_COOKIE['raccookie_guest_email'], or attempt to set a test cookie with that name and monitor if the application attempts to deserialize it
    Affected if The plugin processes that specific cookie via unserialize() means the exploitation path is active
  4. Assess POP chain exposure
    Review all installed plugins and themes for known POP chain gadgets (classes with __wakeup, __destruct, __toString magic methods that can be chained), or use a static analysis tool to scan wp-content for unserialize() calls in other plugins
    Affected if Any other installed plugin or theme contains exploitable POP chain gadgets means the CVE could lead to full remote code execution

You are affected if the WooCommerce Recover Abandoned Cart plugin version is 24.4.0 or lower AND the 'raccookie_guest_email' cookie is processed, AND at least one other installed plugin/theme provides a usable POP chain for impact.

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

Update the plugin to a version beyond 24.4.0 once available, and audit the WordPress installation for other plugins or themes that may contain exploitable POP chains.

Recommended fix Moderate confidence

Latest version available after 24.4.0 (upgrade to the most recent version of the WooCommerce Recover Abandoned Cart plugin)

  1. 1. Check the current version of the WooCommerce Recover Abandoned Cart plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'WooCommerce Recover Abandoned Cart' plugin and note the current version number
  4. 4. Since all versions up to and including 24.4.0 are vulnerable, update the plugin to the latest available version
  5. 5. Go to Plugins > Add New > Upload Plugin (or check for updates via Plugins > Plugin List > Check for Updates)
  6. 6. Install and activate the updated version of the plugin
  7. 7. Verify the update was successful by confirming the new version number in the plugins list
  8. 8. Test that the plugin functionality works correctly after the update
Caveat Review plugin changelog for any breaking changes or deprecated functionality between your current version and the latest version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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