Backuply - Backup, Restore, Migrate and Clone <= 1.2.6 - Denial of Service
Strategic Overview
- Status
- Patched in 1.2.7
- Affected Plugin
- Backuply – Backup, Restore, Migrate and Clone
- Affected Version
<= 1.2.6- CVSS
- 7.5High
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE-2024-0842
At a glance
CVE-2024-0842 is a high-severity Uncontrolled Resource Consumption vulnerability in the Backuply WordPress plugin, affecting versions <= 1.2.6. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.7; sites on affected versions should update now. Disclosed February 2024, reported by villu164.
Vulnerability Overview
The Backuply – Backup, Restore, Migrate and Clone plugin for WordPress is vulnerable to Denial of Service in all versions up to, and including, 1.2.6. This is due to direct access of the backuply/restore_ins.php file and. This makes it possible for unauthenticated attackers to make excessive requests that result in the server running out of resources.
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 availability.
CWE-400: Uncontrolled Resource Consumption
Reaching this weakness in Backuply <= 1.2.6 takes a caller who can reach the endpoint. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. For Backuply the fix is 1.2.7: builds <= 1.2.6 are affected, anything from 1.2.7 onward is not.
Remediation
Update to version 1.2.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Backuply: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Backuply 1.2.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Backuply – Backup, Restore, Migrate and Clone
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C