Summary
CVE-2026-101148 is a critical authentication-bypass vulnerability in the BackupSheep WordPress Backup Plugin, affecting all versions up to and including 1.8. The plugin fails to properly validate its integration key, treating blank or unset keys as valid credentials, which allows unauthenticated attackers to generate and download full site backups (including the database with user password hashes) and to delete arbitrary files on the server. The flaw carries a CVSS v3.1 base score of 10.0 (Critical).
Technical details
- Root cause: The plugin’s integration-key validation logic does not reject empty or unset key values, effectively allowing any request lacking a valid key to be treated as authenticated (CWE-73: External Control of File Name or Path).
- Trigger conditions: The vulnerable integration-key check is reachable on any WordPress installation running the BackupSheep plugin with the key left at its default/blank state, which is the common out-of-the-box condition.
- Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
- Impact: Full confidentiality, integrity, and availability compromise — attackers can create and exfiltrate complete site backups (exposing the database and user password hashes), and delete arbitrary files on the server, which can lead to data breach, credential compromise via offline hash cracking, and denial of service or site takeover.
Affected software
- BackupSheep WordPress Backup Plugin — all versions through 1.8 (inclusive)
- Note: The plugin was removed/closed on WordPress.org in July 2024 and has not received a patch since.
Severity
- CVSS v3.1 Base Score: 10.0 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: No patched version exists. The plugin has been closed on the WordPress.org repository since July 2024 and the vendor has not issued a fix.
- Recommended action: Uninstall and remove the BackupSheep WordPress Backup Plugin from all affected sites immediately, and replace it with an actively maintained backup solution.
- If immediate removal is not possible: Restrict or block external network access to the plugin’s endpoints at the web server or WAF layer, rotate/change any backup-related secrets, and audit existing backup files and server file integrity for signs of unauthorized access or deletion.
- Post-removal: Review site and server logs for anomalous backup-generation or file-deletion requests, and rotate user credentials given the risk of password hash exposure.

