Backup and Restore Wordpress <= 1.50 - Cross-Site Request Forgery to Backup Trigger
Strategic Overview
- Status
- Patched in 2.0.0
- Affected Plugin
- WP BackItUp Community Edition
- Affected Version
<= 1.50- CVSS
- 6.5Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-43269
At a glance
CVE-2024-43269 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP BackItUp Community Edition WordPress plugin, affecting versions <= 1.50. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.0.0; sites on affected versions should update now. Disclosed August 2024, reported by Ananda Dhakal.
Vulnerability Overview
The Backup and Restore WordPress – Backup Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.50. This is due to missing or incorrect nonce validation on the ajax_queue_manual_backup() function. This makes it possible for unauthenticated attackers to trigger backups via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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. A successful exploit has high impact on confidentiality.
CWE-352: Cross-Site Request Forgery (CSRF)
WP BackItUp Community Edition <= 1.50 carries this weakness at ajax_queue_manual_backup(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP BackItUp Community Edition the fix is 2.0.0: builds <= 1.50 are affected, anything from 2.0.0 onward is not.
Remediation
Update to version 2.0.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP BackItUp Community Edition: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP BackItUp Community Edition 2.0.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP BackItUp Community Edition
- 7.5CVE-2014-9012: Backup and Restore WordPress – Backup Info Disclosure
CVE-2014-9012 - 6.5Backup and Restore WordPress – Backup Plugin Authorization Bypass
- 5.3CVE-2025-68039: BackItUp <= 2.1.0 Missing Authorization
CVE-2025-68039 - 5.3CVE-2024-43270: Backup and Restore WordPress Missing Authorization
CVE-2024-43270 - 5.3CVE-2023-7232: Backup and Restore… Information Exposure
CVE-2023-7232 - 4.9CVE-2026-18386: WP BackItUp Community Edition Path Traversal
CVE-2026-18386 - 4.3CVE-2024-43268: Backup and Restore WordPress Missing Authorization
CVE-2024-43268
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C