dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-10913

HIGH · 8.8 CVSS v3.1 Published 2024-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Clone plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.4.6 via deserialization of untrusted input in the 'recursive_unserialized_replace' function. 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 Clone plugin for WordPress contains a PHP Object Injection vulnerability in the 'recursive_unserialized_replace' function, allowing unauthenticated attackers to inject arbitrary PHP objects through deserialization of untrusted input. While no POP chain exists within the plugin itself, if a compatible POP chain is present via another plugin or theme, attackers could achieve arbitrary file deletion, data exfiltration, or code execution.

MitigationUpdate the Clone plugin to version 2.4.7 or later. If an update is unavailable, consider removing the plugin until a patch is released, or implement web application firewall rules to block serialized data in request parameters.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the installed version of the Clone plugin
    Access your WordPress admin dashboard and navigate to Plugins > Installed Plugins, then find the Clone plugin and note the version number displayed. Alternatively, check the main plugin PHP file header for the 'Version' tag.
    Affected if The displayed version is 2.4.6 or lower.
  2. Verify the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, confirm whether the Clone plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin status is Active.
  3. Identify the vulnerable function in plugin code
    Access your WordPress site files via FTP or file manager, locate the Clone plugin directory, and search for the function named 'recursive_unserialized_replace' within the plugin PHP files.
    Affected if The function exists and contains unserialize() calls without proper validation.
  4. Check for untrusted input handling
    Review the plugin code for any $_GET, $_POST, or $_REQUEST parameters being passed to unserialize() or the recursive_unserialized_replace function without sanitization.
    Affected if The plugin processes serialized data from user-supplied input without validation.

You are affected if the Clone plugin version is 2.4.6 or lower, the plugin is currently active, and your installation processes untrusted serialized input through the vulnerable function.

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 Clone plugin to version 2.4.7 or later. If an update is unavailable, consider removing the plugin until a patch is released, or implement web application firewall rules to block serialized data in request parameters.

Recommended fix High confidence

Latest version available in WordPress plugin repository (version higher than 2.4.6)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Clone' plugin in the list
  4. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  5. Verify the updated version is higher than 2.4.6
Caveat Standard WordPress plugin update best practices apply - backup site before updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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