WP Database Backup <= 5.1.2 - Unauthenticated Settings Update to Remote Code Execution

2019-03-24 00:00
Anonymous

Strategic Overview

Status
Patched in 5.1.3
Affected Plugin
WP Database Backup – Unlimited Database & Files Backup by Backup for WP
Affected Version
<= 5.1.2
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all WP Database Backup – Unlimited Database & Files Backup by Backup for WP vulnerabilities

At a glance

This record tracks a critical-severity Missing Authorization vulnerability in the WP Database Backup WordPress plugin, affecting versions <= 5.1.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.1.3; sites on affected versions should update now. Disclosed March 2019.

Vulnerability Overview

The WP Database Backup plugin for WordPress is vulnerable to unauthenticated settings update that can lead to remote code execution via the wpsetting functionality in versions up to, and including, 5.1.2. This makes it possible for unauthenticated attackers to inject malicious code into settings that will execute when a back-up is triggered by an unsuspecting user.

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, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in WP Database Backup <= 5.1.2 takes no account at all. 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 WP Database Backup the fix is 5.1.3: builds <= 5.1.2 are affected, anything from 5.1.3 onward is not.

Remediation

Update to version 5.1.3, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Database Backup 5.1.3 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/f8035ed9-d267-44da-9de4-cf3d6ece7059

Related records

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