CVE-2024-10962

Migration, Backup, Staging – WPvivid <= 0.9.107 - Unauthenticated PHP Object Injection

2024-11-13 00:00
Webbernaut

Strategic Overview

Status
Patched in 0.9.108
Affected Version
<= 0.9.107
CVSS
8.8High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2024-10962
View all WPvivid — Backup, Migration & Staging vulnerabilities

At a glance

CVE-2024-10962 is a high-severity Deserialization of Untrusted Data vulnerability in the WPvivid WordPress plugin, affecting versions <= 0.9.107. 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 0.9.108; sites on affected versions should update now. Disclosed November 2024, reported by Webbernaut.

Vulnerability Overview

The Migration, Backup, Staging – WPvivid plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 0.9.107 via deserialization of untrusted input in the 'replace_row_data' and 'replace_serialize_data' functions. 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. An administrator must create a staging site 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

WPvivid <= 0.9.107 carries this weakness at replace_row_data, 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 WPvivid the fix is 0.9.108: builds <= 0.9.107 are affected, anything from 0.9.108 onward is not.

Remediation

Update to version 0.9.108, 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: WPvivid 0.9.108 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

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