CVE-2014-10076

Database Backup for WordPress <= 2.2.4 - Missing Authorization

2014-11-02 00:00
Larry W. Cashdollar

Strategic Overview

Status
Patched in 2.3.0
Affected Version
<= 2.2.4
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2014-10076
View all Database Backup for WordPress vulnerabilities

At a glance

CVE-2014-10076 is a high-severity Missing Authorization vulnerability in the Database Backup for WordPress WordPress plugin, affecting versions <= 2.2.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.3.0; sites on affected versions should update now. Disclosed November 2014, reported by Larry W. Cashdollar.

Vulnerability Overview

The wp-db-backup plugin up to 2.2.4 for WordPress relies on a five-character string for access control, which makes it easier for remote attackers to read backup archives via a brute-force attack.

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-862: Missing Authorization

Reaching this weakness in Database Backup for WordPress <= 2.2.4 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Database Backup for WordPress the fix is 2.3.0: builds <= 2.2.4 are affected, anything from 2.3.0 onward is not.

Remediation

Update to version 2.3.0, 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: Database Backup for WordPress 2.3.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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