BackUpWordPress: logged-in users can delete backup protection files, fixed in 3.15
Identifiers: CVE-2026-104307
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
BackUpWordPress, plugin slug backupwordpress, lacks a capability and nonce check on the AJAX action used to dismiss error notices in versions before 3.15, tracked as CVE-2026-104307. Any authenticated user, including the Subscriber role, can trigger it to delete files in the backup directory: the .htaccess file that protects backups from direct download, and working files such as database dumps still in progress. WPScan published the issue on 6 November 2026, the CVE record followed on 8 November, and the vendor changelog for 3.15 is dated 4 November 2026.
Impact
A low-privileged account can remove the plugin's own download protection for the backup directory and disrupt running backup jobs. The issue is not unauthenticated, and the reported and verified scope is limited to the protection file and working files in the backup directory; the sources do not show that backups were actually downloaded or that other web server controls were removed. Whether backup archives become reachable from the internet depends on your web server configuration, which the sources do not cover.
Who is affected
Sites running BackUpWordPress below 3.15 with any authenticated account, including the Subscriber role; a single-user site is affected if that one account is compromised. Multiple accounts or open registration, such as customers and commenters, increase the risk but are not required. Sites on 3.15 or newer have the fix, but updating does not by itself establish that missing files are restored or that older backup copies are protected; verify the download rules and backup integrity separately.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| BackUpWordPress | < 3.15 | 3.15 |
Exploitation evidence
Exploitation not established. No exploitation in the wild is established in the reviewed sources. The low privilege needed makes attempts plausible, so do not rely on this as reassurance.
Actions
- Confirm whether the plugin is installed and which exact version is active.
- Before changing anything, keep a recoverable backup copy outside the live web root with appropriately limited access; do not delete your only backup or disable backups you need.
- Update to 3.15 or a newer patched release in a controlled way, then run a scheduled backup and test that restore works and that the download access rules are back in place.
- Ask your provider to check for missing protection files, missing or truncated working files, and relevant log entries.
- If compromise is confirmed under the provider's investigation, replace damaged backup copies and rotate any secrets that may have been exposed.
Unknowns
- Whether other web server controls on your host would still block direct access to the backup directory if the .htaccess file is removed.
- Whether anyone deleted files or accessed backups before the update; the reviewed sources do not address this.
Sources
- WPScan https://wpscan.com/vulnerability/fdd1c029-f055-40c0-9c7f-a0a3822304a9/
- WPScan / CVE Program https://cveawg.mitre.org/api/cve/CVE-2026-104307
- Plugin vendor / WordPress SVN https://plugins.svn.wordpress.org/backupwordpress/trunk/readme.txt
- Patchstack https://patchstack.com/database/wordpress/plugin/backupwordpress/vulnerability/wordpress-backupwordpress-plugin-3-15-subscriber-backup-directory-file-deletion-vulnerability
Change history
- — Published: Published 9 November 2026 from the WPScan report of 6 November 2026 and the vendor patch 3.15 dated 4 November 2026.