Database Backup for WordPress <= 2.5.2 - Missing Authorization to Unauthenticated Arbitrary File Read and Deletion
Strategic Overview
- Status
- Patched in 2.5.3
- Affected Plugin
- Database Backup for WordPress
- Affected Version
<= 2.5.2- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-4030
At a glance
CVE-2026-4030 is a high-severity Missing Authorization vulnerability in the Database Backup for WordPress WordPress plugin, affecting versions <= 2.5.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.5.3; sites on affected versions should update now. Disclosed May 2026, reported by Drew Webber (mcdruid).
Vulnerability Overview
The Database Backup for WordPress plugin for WordPress is vulnerable to unauthorized arbitrary file read and deletion in all versions up to, and including, 2.5.2. This is due to the plugin not properly enforcing the return value of its authorization check combined with a user-controlled backup directory parameter. This makes it possible for unauthenticated attackers to read and delete arbitrary files on the server, leading to Sensitive Information Exposure and potential site takeover. Note: This vulnerability is only exploitable in WordPress Multisite environments where the deprecated is_site_admin() function exists.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, 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-862: Missing Authorization
Database Backup for WordPress <= 2.5.2 carries this weakness at is_site_admin(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Database Backup for WordPress the fix is 2.5.3: builds <= 2.5.2 are affected, anything from 2.5.3 onward is not.
Remediation
Update to version 2.5.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Database Backup for WordPress 2.5.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Database Backup for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C