CVE-2020-7241

WP Database Backup <= 5.5 - Unauthenticated Information Disclosure

2020-02-06 00:00
V1n1v131r4

Strategic Overview

Status
Patched in 5.5.1
Affected Plugin
WP Database Backup – Unlimited Database & Files Backup by Backup for WP
Affected Version
<= 5.5
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2020-7241
View all WP Database Backup – Unlimited Database & Files Backup by Backup for WP vulnerabilities

At a glance

CVE-2020-7241 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Database Backup WordPress plugin, affecting versions <= 5.5. 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 5.5.1; sites on affected versions should update now. Disclosed February 2020, reported by V1n1v131r4.

Vulnerability Overview

The WP Database Backup plugin through 5.5 for WordPress stores downloads by default locally in the directory wp-content/uploads/db-backup/. This might allow attackers to read ZIP archives by guessing random ID numbers, guessing date strings with a 2020_{0..1}{0..2}_{0..3}{0..9} format, guessing UNIX timestamps, and making HTTPS requests with the complete guessed URL.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in WP Database Backup <= 5.5 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP Database Backup the fix is 5.5.1: builds <= 5.5 are affected, anything from 5.5.1 onward is not.

Remediation

Update to version 5.5.1, 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.5.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-7241https://www.wordfence.com/threat-intel/vulnerabilities/id/c58a2de0-8bb3-4e48-889e-0a8f47ca2959https://nvd.nist.gov/vuln/detail/CVE-2020-7241

Related records

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