Backup Migration <= 1.3.9 - Unauthenticated Path Traversal to Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 1.4.0
- Affected Plugin
- Backup Migration
- Affected Version
<= 1.3.9- CVSS
- 9.8Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2023-6972
At a glance
CVE-2023-6972 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Backup Migration WordPress plugin, affecting versions <= 1.3.9. 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 1.4.0; sites on affected versions should update now. Disclosed December 2023, reported by Hiroho Shimada.
Vulnerability Overview
The Backup Migration plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.3.9 via the 'content-backups' and 'content-name', 'content-manifest', or 'content-bmitmp' and 'content-identy' HTTP headers. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and remote code execution possible.
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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Backup Migration <= 1.3.9 carries this weakness at content-backups, and reaching it takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Backup Migration the fix is 1.4.0: builds <= 1.3.9 are affected, anything from 1.4.0 onward is not.
Remediation
Update to version 1.4.0, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Backup Migration 1.4.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Backup Migration
- 9.8CVE-2023-6553: Backup Migration <= 1.3.7 Remote Code Execution
CVE-2023-6553 - 9.8CVE-2023-6271: Backup Migration <= 1.3.5 Info Exposure
CVE-2023-6271 - 8.8CVE-2024-10932: Backup Migration <= 1.4.6 PHP Object Injection
CVE-2024-10932 - 8.1CVE-2023-6971: Backup Migration 1.0.8 - 1.3.9 Remote File Inclusion
CVE-2023-6971 - 7.5CVE-2025-12394: Backup Migration Information Exposure
CVE-2025-12394 - 7.5CVE-2023-6266: Backup Migration Arbitrary Backup Download
CVE-2023-6266 - 7.5CVE-2023-54346: Backup Migration <= 1.2.8 Info Exposure
CVE-2023-54346 - 7.2CVE-2026-7693: Backup Migration <= 2.1.5.1 OS Command Injection
CVE-2026-7693
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C