BlogVault WordPress Backup Plugin 1.40 - 1.44 - Unauthenticated PHP Object Injection
Strategic Overview
- Status
- Patched in 1.45
- Affected Plugin
- BlogVault Backup & Staging
- Affected Version
1.40 – 1.44- CVSS
- 8.3High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE pending
At a glance
This record tracks a high-severity Deserialization of Untrusted Data vulnerability in the BlogVault Backup & Staging WordPress plugin, affecting versions 1.40 – 1.44. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.45; sites on affected versions should update now. Disclosed April 2017.
Vulnerability Overview
The BlogVault WordPress Backup Plugin for WordPress is vulnerable to PHP Object Injection in versions 1.40 - 1.44 via deserialization of untrusted input in the vulnerable function processApiRequest. This allows unauthenticated attackers to inject a PHP Object. No POP chain is present in the vulnerable plugin. 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 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, and no interaction from a victim user.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in BlogVault Backup & Staging 1.40 – 1.44 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 BlogVault Backup & Staging the fix is 1.45: builds 1.40 – 1.44 are affected, anything from 1.45 onward is not.
Remediation
Update to version 1.45, 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: BlogVault Backup & Staging 1.45 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in BlogVault Backup & Staging
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C