CVE-2026-101148: BackupSheep WordPress Plugin Broken Key Validation Authentication Bypass & Site Wipe
HERMES THREAT SCORE & CMS INFRASTRUCTURE EXPOSURE
Target:BackupSheep WordPress Backup Plugin โ Automated Cloud Backup & REST Callback Controller Standard CVSS v3.1 rates this flaw at a maximum 10.0 (Critical). The Hermes Threat Score (HTS) evaluates it at 93 (CRITICAL). This zero-day vulnerability in the BackupSheep backup plugin allows unauthenticated adversaries to directly trigger on-demand backups and download complete database dumps containing hashed administrator passwords, authentication salts, and confidential content. Furthermore, an exposed file deletion routine enables unauthenticated attackers to wipe arbitrary files such as wp-config.php, triggering the WordPress initial setup wizard to seize administrator ownership. Because the plugin was abandoned and closed on WordPress.org without an official fix, vulnerable installations require immediate manual deactivation and removal.
CVE-2026-101148: BackupSheep WordPress Plugin Broken Key Validation Authentication Bypass & Site WipeVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in BackupSheep WordPress Backup Plugin documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Software Matrix
Section titled โ1. Technical Context & Affected Software MatrixโThe BackupSheep plugin was developed to bridge self-hosted WordPress installations with the BackupSheep cloud backup automation platform, providing scheduled database backups, offsite storage replication, and file restoration routines.
| Parameter | Technical Specification | Operational Impact |
|---|---|---|
| CVE Identifier | CVE-2026-101148 | Global tracking reference |
| Advisory Source | NVD / Patchstack Vulnerability Database | Critical CMS zero-day advisory (October 1, 2026) |
| Vulnerability Class | Authentication Bypass (CWE-287), Missing Authentication (CWE-306), Insecure File Operations (CWE-732) | Complete site takeover & destructive file erasure |
| Affected Components | BackupSheep REST API Endpoints (/wp-json/backupsheep/v1/), AJAX Handlers | Backup generation, archive download, and file cleanup routines |
| Affected Versions | BackupSheep WordPress Plugin <= 1.8 | All deployed installations |
| Fixed Version | None (Abandoned / Closed on WordPress.org) | Immediate plugin removal required |
| Operational Impact | Total WordPress CMS & Database Compromise | Password hash exfiltration, wp-config.php deletion, site hijacking |
2. In-Depth Technical Decomposition
Section titled โ2. In-Depth Technical DecompositionโThe Flaw: Loose Type Equality on Uninitialized API Keys
Section titled โThe Flaw: Loose Type Equality on Uninitialized API KeysโWhen the BackupSheep service initiates a remote backup or checks connectivity, it sends an HTTP request containing the userโs API key. The plugin inspects this key inside its authentication handler:
UNAUTHENTICATED ATTACKER WORDPRESS REST API / BACKUPSHEEP WORDPRESS MYSQL DATABASE & DISK โ โ โ โ 1. HTTP POST /wp-json/backupsheep/v1/backup โ โ โ Header: (No X-BackupSheep-Key supplied) โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ โ 2. Evaluate Stored Key: โ โ โ $stored = get_option('backupsheep_key'); โ โ โ $incoming = $_SERVER['HTTP_X_KEY'] ?? '';โ โ โ Is $stored == $incoming? โ โ โ Both evaluate to empty string ("" == "")!โ โ โ PHP evaluates: TRUE (Authenticated!) โ โ โ โ โ โ 3. Execute Backup Generation: โ โ โ Triggers mysqldump & archive bundling โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ Writes backup-2026-10-01.zip to disk โ โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ โ โ โ 4. HTTP 200 OK: Backup Archive URL Returned โ โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ โ โ โ โ 5. Download Full Database & wp-config.php โ โ โ GET /wp-content/uploads/backupsheep/... โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ Complete Database Dump (User Hashes, WooCommerce Orders, API Secrets Exfiltrated) โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโคIn PHP, the loose comparison operator == does not check variable types. If an administrator installs the plugin but does not complete the cloud registration wizard, get_option('backupsheep_api_key') returns false or an empty string "". An attacker sending an empty string or omitting the header entirely causes $incoming_key == $stored_key to evaluate to true.
Furthermore, the plugin exposes a file deletion endpoint (/wp-json/backupsheep/v1/delete) designed to clean up temporary archives. This endpoint accepts an arbitrary path parameter without verifying that the file resides within the designated backup folder. By providing the path to wp-config.php, the attacker causes WordPress to lose its database connection settings, prompting WordPress to serve the initial installation page (/wp-admin/install.php) where the attacker can register as the primary site administrator.
Vulnerable Code Pattern (Conceptual Plugin Extract)
Section titled โVulnerable Code Pattern (Conceptual Plugin Extract)โ<?php// Vulnerable implementation in BackupSheep WordPress plugin (<= 1.8)
add_action('rest_api_init', function () { register_rest_route('backupsheep/v1', '/backup', [ 'methods' => 'POST', 'callback' => 'backupsheep_trigger_backup_endpoint', 'permission_callback' => 'backupsheep_verify_auth_request', ]);
register_rest_route('backupsheep/v1', '/delete', [ 'methods' => 'POST', 'callback' => 'backupsheep_delete_file_endpoint', 'permission_callback' => 'backupsheep_verify_auth_request', ]);});
function backupsheep_verify_auth_request($request) { // VULNERABILITY (CWE-287): Weak authentication check $incoming_key = $request->get_header('X-BackupSheep-Key') ?? ''; $stored_key = get_option('backupsheep_api_key');
// If unconfigured, $stored_key is empty/false. Loose equality "" == false is TRUE! if ($incoming_key == $stored_key) { return true; } return new WP_Error('rest_forbidden', 'Unauthorized', ['status' => 403]);}
function backupsheep_delete_file_endpoint($request) { $file_path = $request->get_param('file_path');
// VULNERABILITY (CWE-732): Arbitrary file deletion without path boundary check! if (file_exists($file_path)) { unlink($file_path); // Attacker can supply ABSPATH . 'wp-config.php' return rest_ensure_response(['success' => true, 'deleted' => $file_path]); } return new WP_Error('not_found', 'File not found', ['status' => 404]);}Remediated Logic (Strict Authorization & Boundary Enforcement)
Section titled โRemediated Logic (Strict Authorization & Boundary Enforcement)โ<?php// Secure implementation: strict typing, non-empty validation, and directory jail
function backupsheep_verify_auth_request_secure($request) { $incoming_key = (string) $request->get_header('X-BackupSheep-Key'); $stored_key = (string) get_option('backupsheep_api_key', '');
// REMEDIATION: Disallow empty keys and require cryptographically safe constant-time comparison if (empty($incoming_key) || empty($stored_key)) { return new WP_Error('rest_forbidden', 'Integration key not configured', ['status' => 403]); }
if (!hash_equals($stored_key, $incoming_key)) { return new WP_Error('rest_forbidden', 'Invalid credentials', ['status' => 403]); }
return true;}
function backupsheep_delete_file_endpoint_secure($request) { $filename = basename((string) $request->get_param('filename')); $backup_dir = wp_upload_dir()['basedir'] . '/backupsheep/'; $target_file = realpath($backup_dir . $filename);
// REMEDIATION: Enforce strict path prefix check inside backup directory only if ($target_file === false || strpos($target_file, realpath($backup_dir)) !== 0) { return new WP_Error('forbidden_path', 'Access denied outside backup folder', ['status' => 403]); }
if (unlink($target_file)) { return rest_ensure_response(['success' => true]); } return new WP_Error('delete_failed', 'Could not delete file', ['status' => 500]);}3. Attack Vectors & Real-World Weaponization
Section titled โ3. Attack Vectors & Real-World WeaponizationโAutomated botnets and vulnerability scanners scan for the BackupSheep plugin footprint to execute multi-stage site compromises:
- Mass Discovery of Unconfigured Plugins: Attackers scan for endpoints matching
/wp-json/backupsheep/v1/or checkwp-content/plugins/backupsheep/readme.txtto identify vulnerable targets. - Database Dumping & PII Harvesting: By sending an empty POST request to
/wp-json/backupsheep/v1/backup, the attacker triggers an immediate database export. The resultant archive contains user password hashes, customer payment details, private store orders, and active plugin secrets. - Site Hijacking via wp-config.php Deletion: In instances where database password cracking is unfeasible, attackers call
/wp-json/backupsheep/v1/deletewithfile_path=.../wp-config.php. Deletingwp-config.phpforces WordPress into setup mode. The attacker accesses/wp-admin/install.php, connects the site to an external attacker-controlled database, and provisions a new administrator account, fully usurping domain control. - Denial of Service & Ransom Demands: Attackers invoke the deletion routine iteratively across all theme files, uploads, and core PHP scripts, holding the site owner to ransom for restoration.
4. Forensic Triage & Detection Engineering
Section titled โ4. Forensic Triage & Detection EngineeringโSOC and incident response analysts should inspect web server access logs for anomalous requests to the BackupSheep REST endpoints.
title: BackupSheep WordPress Plugin Unauthenticated Backup or File Deletion (CVE-2026-101148)id: b892d104-1011-482a-9e12-85cbe101148bstatus: experimentaldescription: Detects HTTP requests directed to BackupSheep WordPress plugin REST API endpoints indicative of authentication bypass exploitation.author: Hermes Codex Cyber Intelligencedate: 2026-10-01references: - https://nvd.nist.gov/vuln/detail/CVE-2026-101148 - https://patchstack.com/databaselogsource: category: webserver product: wordpressdetection: selection_uri: cs-uri-stem|contains: - '/wp-json/backupsheep/v1/' - 'backupsheep_trigger_backup' - 'backupsheep_delete_file' selection_method: cs-method: - 'POST' - 'GET' condition: selection_uri and selection_methodfields: - c-ip - cs-method - cs-uri-stem - sc-status - cs-user-agentfalsepositives: - Legitimate requests originating from confirmed BackupSheep cloud IP ranges with valid API keyslevel: criticaltags: - attack.initial_access - attack.t1190 - attack.impact - attack.t1485 - cve.2026.101148// Azure Sentinel: Detect BackupSheep REST API exploitation and file deletionW3CIISLog| where TimeGenerated >= ago(7d)| where csUriStem has "/wp-json/backupsheep/v1/"| where csMethod == "POST"| where scStatus in (200, 201)| project TimeGenerated, cIP, sIP, csMethod, csUriStem, scStatus, csUserAgent| order by TimeGenerated desc#!/bin/bash# WP-CLI Forensic Audit: Check for BackupSheep plugin presence and anomalous filesecho "[*] Auditing WordPress root for BackupSheep vulnerability (CVE-2026-101148)..."
# 1. Check if the BackupSheep plugin is installedif [ -d "wp-content/plugins/backupsheep" ]; then echo "[!] CRITICAL: BackupSheep plugin found in wp-content/plugins/backupsheep!" echo "[!] This plugin is abandoned and vulnerable to CVE-2026-101148."
# 2. Check for recent backup archives created in upload folders echo "[*] Searching for exposed backup files in wp-content/uploads/..." find wp-content/uploads/ -type f \( -name "*backupsheep*" -o -name "*.sql" -o -name "*.zip" \) -mtime -14 -ls
# 3. Prompt for immediate deactivation and removal echo "[+] To immediately remediate, run:" echo " wp plugin deactivate backupsheep --uninstall" echo " rm -rf wp-content/plugins/backupsheep"else echo "[+] BackupSheep plugin is not installed in this WordPress environment."fi5. Remediation Strategy & Hardening
Section titled โ5. Remediation Strategy & Hardeningโ-
Deactivate and Permanently Delete BackupSheep Immediately:
Because the plugin is unmaintained and closed on WordPress.org, no patch exists. Remove the plugin directory completely:Terminal window wp plugin deactivate backupsheep --uninstallrm -rf wp-content/plugins/backupsheep/ -
Audit Uploads and Purge Dangling Backup Archives:
Inspectwp-content/uploads/for lingering.sqlor.ziparchives generated by the plugin and delete them immediately to prevent public scraping. -
Rotate WordPress Database Passwords and Security Salts:
If the site operated with BackupSheep installed, assume the database has been downloaded. Update the database user password inwp-config.php, update MySQL user permissions, and regenerate all authentication keys and salts inwp-config.phpviahttps://api.wordpress.org/secret-key/1.1/salt/. -
Reset All WordPress Administrator Passwords:
Force password resets for all users withadministrator,editor, andshop_managerprivileges to invalidate any cracked hashes. -
Deploy WAF Virtual Patching:
Configure Web Application Firewall rules to block all traffic targeting/wp-json/backupsheep/at the edge:# Nginx block rule for BackupSheep endpointslocation ~* /wp-json/backupsheep/ {return 403;}