All-in-One WP Migration <= 2.0.4 - Missing Authorization to Database Export

2015-03-19 00:00
James Golovich

Strategic Overview

Status
Patched in 2.0.5
Affected Plugin
All-in-One WP Migration and Backup
Affected Version
<= 2.0.4
CVSS
7.5High
Weakness type
CWE-287 · Improper Authentication
CVE
CVE pending
View all All-in-One WP Migration and Backup vulnerabilities

At a glance

This record tracks a high-severity Improper Authentication vulnerability in the All-in-One WP Migration and Backup WordPress plugin, affecting versions <= 2.0.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.0.5; sites on affected versions should update now. Disclosed March 2015, reported by James Golovich.

Vulnerability Overview

The All-in-One WP Migration plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the 'router()' function in versions up to, and including, 2.0.4. This makes it possible for unauthenticated attackers to export a complete copy of the vulnerable service's database.

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. A successful exploit has high impact on confidentiality.

CWE-287: Improper Authentication

All-in-One WP Migration and Backup <= 2.0.4 carries this weakness at router(), and reaching it takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For All-in-One WP Migration and Backup the fix is 2.0.5: builds <= 2.0.4 are affected, anything from 2.0.5 onward is not.

Remediation

Update to version 2.0.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: All-in-One WP Migration and Backup 2.0.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/95cd2bae-4ab7-4a0c-bb71-c17b119eaaa9

Related records

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