WP All Backup <= 2.4.3 - Cross-Site Request Forgery to Backup Storage Modification
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP All Backup
- Affected Version
<= 2.4.3- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-32583
At a glance
CVE-2023-32583 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP All Backup WordPress plugin, affecting versions <= 2.4.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2023, reported by Kévin Mosbahi (Mika).
Vulnerability Overview
The WP All Backup plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4.3. This is due to missing nonce validation on the wp_all_backup_admin_init() function called via admin_init. This makes it possible for unauthenticated attackers to perform multiple actions such as deleting back-ups, starting back-ups, and restoring back-ups 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.
CWE-352: Cross-Site Request Forgery (CSRF)
WP All Backup <= 2.4.3 carries this weakness at wp_all_backup_admin_init(), 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. No fixed build of this plugin is recorded for WP All Backup yet, so installs running <= 2.4.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP All Backup: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C