Backuply – Backup, Restore, Migrate and Clone <= 1.2.7 - Authenticated (Admin+) Directory Traversal
Strategic Overview
- Status
- Patched in 1.2.8
- Affected Plugin
- Backuply – Backup, Restore, Migrate and Clone
- Affected Version
<= 1.2.7- CVSS
- 4.9Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-2294
At a glance
CVE-2024-2294 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Backuply WordPress plugin, affecting versions <= 1.2.7. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.2.8; sites on affected versions should update now. Disclosed March 2024, reported by Dau Hoang Tai.
Vulnerability Overview
The Backuply – Backup, Restore, Migrate and Clone plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.2.7 via the backup_name parameter in the backuply_download_backup function. This makes it possible for attackers to have an account with only activate_plugins capability to access arbitrary files on the server, which can contain sensitive information. This only impacts sites hosted on Windows servers.
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 interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Backuply <= 1.2.7 takes an account at Admin level or above. 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 Backuply the fix is 1.2.8: builds <= 1.2.7 are affected, anything from 1.2.8 onward is not.
Remediation
Update to version 1.2.8, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Backuply 1.2.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Backuply – Backup, Restore, Migrate and Clone
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C