dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-12313

HIGH · 8.1 CVSS v3.1 Published 2025-01-07
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 Compare Products for WooCommerce plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.2.1 via deserialization of untrusted input from the 'woo_compare_list' cookie. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 Compare Products for WooCommerce plugin for WordPress is vulnerable to PHP Object Injection via unsafe deserialization of the 'woo_compare_list' cookie. Unauthenticated attackers can inject arbitrary PHP objects. While no POP chain exists in the plugin itself, additional plugins or themes on the target system could provide one, potentially allowing arbitrary file deletion, data exfiltration, or code execution.

MitigationUpdate the plugin to a patched version once available. If no patch is imminent, disable the plugin or implement input validation to prevent deserialization of untrusted cookie data. Consider using JSON encoding instead of PHP serialization for the compare list functionality.

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 plugin installation
    Check if Compare Products for WooCommerce plugin is installed in WordPress: navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for a folder containing 'compare-products-for-woocommerce' or similar naming. Query database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if Plugin appears in the active plugins list or filesystem
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Compare Products for WooCommerce entry; the version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for 'Version:' comment, or read /wp-content/plugins/[plugin-folder]/readme.txt for the stable tag.
    Affected if Version is at or below any unpatched release (compare to vendor advisory once patched version is published)
  3. Confirm cookie processing is active
    Monitor HTTP requests to the site and inspect cookies. Check if a cookie named 'woo_compare_list' is present and contains serialized PHP data (look for patterns like 'O:number' or 'a:number' indicating PHP serialization). Alternatively, inspect the plugin code for unserialize() calls on $_COOKIE['woo_compare_list'].
    Affected if The woo_compare_list cookie is present and the plugin deserializes its value without validation
  4. Check for POP chain sources
    Audit installed plugins and themes for known POP chain gadgets: look for __destruct or __wakeup methods in any active plugin/theme code under /wp-content/plugins/ and /wp-content/themes/. Cross-reference with known vulnerable plugins (e.g., WooCommerce, popular page builders, or any plugin with file operations or SQL queries in magic methods).
    Affected if Additional plugins with exploitable unserialize gadgets are present on the system

The environment is affected if the Compare Products for WooCommerce plugin is installed, processes the woo_compare_list cookie via unserialize, and a POP chain gadget exists elsewhere on the WordPress installation.

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 patched version once available. If no patch is imminent, disable the plugin or implement input validation to prevent deserialization of untrusted cookie data. Consider using JSON encoding instead of PHP serialization for the compare list functionality.

Recommended fix Moderate confidence

Latest version newer than 3.2.1 from WordPress plugin repository

  1. Check the current version of the Compare Products for WooCommerce plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Compare Products for WooCommerce plugin and note the current version number
  4. Visit the WordPress plugin repository page for Compare Products for WooCommerce to check if a newer version is available
  5. If a version newer than 3.2.1 is available, update the plugin to the latest version
  6. After updating, verify the plugin is functioning correctly on your WooCommerce store
  7. If no update is available, consider temporarily disabling the plugin until a security patch is released
  8. Review other installed plugins and themes for any known POP chain vulnerabilities that could be chained with this deserialization issue

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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