dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-10957

HIGH · 8.8 CVSS v3.1 Published 2025-01-04
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 UpdraftPlus: WP Backup & Migration Plugin plugin for WordPress is vulnerable to PHP Object Injection in all versions from 1.23.8 to 1.24.11 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, 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. An administrator must perform a search and replace action to trigger the exploit.

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 UpdraftPlus WordPress plugin versions 1.23.8 to 1.24.11 contains a PHP Object Injection vulnerability in the recursive_unserialized_replace function through which unauthenticated attackers can inject arbitrary PHP objects via deserialization of untrusted input. While no POP chain exists within the plugin itself, the vulnerability can be weaponized if other plugins or themes with POP chains are present on the target system. Exploitation requires an administrator to perform a search and replace action.

MitigationUpdate UpdraftPlus to the latest version beyond 1.24.11 to patch the deserialization vulnerability. Audit installed plugins and themes for known POP chains as they could be leveraged in conjunction with this vulnerability.

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. Verify UpdraftPlus plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for UpdraftPlus, or check the /wp-content/plugins/ directory for the updraftplus folder
    Affected if UpdraftPlus plugin is present on the WordPress site
  2. Identify installed UpdraftPlus version
    In WordPress admin, go to Plugins > Installed Plugins > UpdraftPlus and read the version number displayed, or check the version in updraftplus/wp-updraftplus.php header comment
    Affected if Version is 1.23.8, 1.23.9, 1.23.10, 1.23.11, 1.23.12, 1.24.0, 1.24.1, 1.24.2, 1.24.3, 1.24.4, 1.24.5, 1.24.6, 1.24.7, 1.24.8, 1.24.9, 1.24.10, or 1.24.11 (versions between 1.23.8 and 1.24.11 inclusive)
  3. Check if search and replace feature is accessible
    In WordPress admin, navigate to UpdraftPlus > Settings or Tools > look for a search and replace or migrate/import feature that handles serialized data
    Affected if The search and replace or migration feature is available to administrators
  4. Audit other plugins and themes for POP chain potential
    Review installed plugins and themes for known PHP unserialize vulnerabilities or deserialization POP chains; check plugin/theme directories in /wp-content/plugins/ and /wp-content/themes/
    Affected if Any other installed plugin or theme contains a known POP chain or deserialization gadget that could be combined with this vulnerability

The site is affected if UpdraftPlus version is between 1.23.8 and 1.24.11 inclusive AND an administrator can access the search and replace feature AND other vulnerable plugins/themes with POP chains exist on the system.

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 UpdraftPlus to the latest version beyond 1.24.11 to patch the deserialization vulnerability. Audit installed plugins and themes for known POP chains as they could be leveraged in conjunction with this vulnerability.

Recommended fix Moderate confidence

Version 1.24.12 or latest available version

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find the UpdraftPlus: WP Backup & Migration Plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is 1.24.12 or higher

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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