All-in-One WP Migration <= 2.0.2 - Authorization Bypass to Arbitrary File Upload

2014-11-05 00:00
Kacper Szurek

Strategic Overview

Status
Patched in 2.0.3
Affected Plugin
All-in-One WP Migration and Backup
Affected Version
<= 2.0.2
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE pending
View all All-in-One WP Migration and Backup vulnerabilities

At a glance

This record tracks a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the All-in-One WP Migration and Backup WordPress plugin, affecting versions <= 2.0.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed November 2014, reported by Kacper Szurek.

Vulnerability Overview

The All-in-One WP Migration plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the import() function in versions up to, and including, 2.0.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to upload arbitrary files.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

All-in-One WP Migration and Backup <= 2.0.2 carries this weakness at import(), and reaching it takes a caller who can reach the endpoint. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For All-in-One WP Migration and Backup the fix is 2.0.3: builds <= 2.0.2 are affected, anything from 2.0.3 onward is not.

Remediation

Update to version 2.0.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to All-in-One WP Migration and Backup: 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: All-in-One WP Migration and Backup 2.0.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/66b91fe9-ceb3-485c-bf5f-a672656d4e86

Related records

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