CVE-2024-10932

Backup Migration <= 1.4.6 - Unauthenticated PHP Object Injection via 'recursive_unserialize_replace'

2025-01-03 00:00
Webbernaut

Strategic Overview

Status
Patched in 1.4.6.1
Affected Plugin
Backup Migration
Affected Version
<= 1.4.6
CVSS
8.8High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2024-10932
View all Backup Migration vulnerabilities

At a glance

CVE-2024-10932 is a high-severity Deserialization of Untrusted Data vulnerability in the Backup Migration WordPress plugin, affecting versions <= 1.4.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.6.1; sites on affected versions should update now. Disclosed January 2025, reported by Webbernaut.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Backup Migration <= 1.4.6 carries this weakness at recursive_unserialize_replace, and reaching it takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Backup Migration the fix is 1.4.6.1: builds <= 1.4.6 are affected, anything from 1.4.6.1 onward is not.

Remediation

Update to version 1.4.6.1, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Backup Migration 1.4.6.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2024-10932https://www.wordfence.com/threat-intel/vulnerabilities/id/d5a0c514-5200-47f4-9d2e-684d68946b9ahttps://nvd.nist.gov/vuln/detail/CVE-2024-10932

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C