dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-10932

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 Backup Migration plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.4.6 via deserialization of untrusted input in the 'recursive_unserialize_replace' function. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to delete arbitrary files, retrieve sensitive data, or execute code. An administrator must create a staging site in order 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 Backup Migration WordPress plugin is vulnerable to PHP Object Injection via the 'recursive_unserialize_replace' function in versions up to 1.4.6. Unauthenticated attackers can deserialize untrusted input to inject PHP objects, and the presence of a POP chain enables arbitrary file deletion, data exfiltration, or remote code execution. Exploitation requires an administrator to first create a staging site.

MitigationUpdate the Backup Migration plugin to version 1.4.7 or later. Until patched, restrict administrative staging site creation capabilities and monitor for unusual deserialization activity.

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. Confirm Backup Migration plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Backup Migration' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active.
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name to view details, or inspect the plugin header in wp-content/plugins/backup-migration/backup-migration.php for the 'Version' comment.
    Affected if The version number is 1.4.6 or lower.
  3. Check if a staging site exists
    Look for a staging site in the WordPress admin under Backup Migration settings, or check the wp_options table for options containing 'staging' or 'backup_migration_staging'. Also check the wp-content/backup-migration/ directory for staging-related subfolders.
    Affected if A staging site has been created by an administrator.
  4. Review access to staging site creation
    In WordPress admin, verify which user roles can access the Backup Migration staging functionality. Check under Users > All Users or the plugin's user capability settings.
    Affected if Roles other than Administrator can create staging sites, or the functionality is accessible to unauthenticated users.

You are affected if the Backup Migration plugin version is 1.4.6 or lower AND a staging site has been created, allowing unauthenticated PHP object injection via the recursive_unserialize_replace 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 Backup Migration plugin to version 1.4.7 or later. Until patched, restrict administrative staging site creation capabilities and monitor for unusual deserialization activity.

Recommended fix High confidence

Backup Migration plugin version 1.4.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Backup Migration' plugin
  4. If an update is available, click 'Update Now' to update to the latest version (1.4.7 or later)
  5. Alternatively, enable automatic plugin updates to ensure future security patches are applied promptly
  6. Verify the plugin version after update to confirm the fix is applied

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-10932 — 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-10932 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