CVE-2023-6266

Backup Migration <= 1.3.6 - Unauthenticated Arbitrary Backup Download to Sensitive Information Exposure

2023-11-30 00:00
Rafshanzani Suhada

Strategic Overview

Status
Patched in 1.3.7
Affected Plugin
Backup Migration
Affected Version
<= 1.3.6
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-6266
View all Backup Migration vulnerabilities

At a glance

CVE-2023-6266 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Backup Migration WordPress plugin, affecting versions <= 1.3.6. 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 1.3.7; sites on affected versions should update now. Disclosed November 2023, reported by Rafshanzani Suhada.

Vulnerability Overview

The Backup Migration plugin for WordPress is vulnerable to unauthorized access of data due to insufficient path and file validation on the BMI_BACKUP case of the handle_downloading function in all versions up to, and including, 1.3.6. This makes it possible for unauthenticated attackers to download back-up files which can contain sensitive information such as user passwords, PII, database credentials, and much more.

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 Backup Migration <= 1.3.6 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 Backup Migration the fix is 1.3.7: builds <= 1.3.6 are affected, anything from 1.3.7 onward is not.

Remediation

Update to version 1.3.7, 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: Backup Migration 1.3.7 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