Skip to content

CVE-2026-101148: BackupSheep WordPress Plugin Broken Key Validation Authentication Bypass & Site Wipe

Density:
HTS

HERMES THREAT SCORE & CMS INFRASTRUCTURE EXPOSURE

Target: BackupSheep WordPress Backup Plugin โ€” Automated Cloud Backup & REST Callback Controller
Confidence: 98%
93 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 18 / 20
Prevalence 16 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

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.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-101148: BackupSheep WordPress Plugin Broken Key Validation Authentication Bypass & Site WipeVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTBackupSheep WordPress Backup Plugin
98% VERY_HIGH

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.”

Supporting Verified Evidence:

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.

ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-101148Global tracking reference
Advisory SourceNVD / Patchstack Vulnerability DatabaseCritical CMS zero-day advisory (October 1, 2026)
Vulnerability ClassAuthentication Bypass (CWE-287), Missing Authentication (CWE-306), Insecure File Operations (CWE-732)Complete site takeover & destructive file erasure
Affected ComponentsBackupSheep REST API Endpoints (/wp-json/backupsheep/v1/), AJAX HandlersBackup generation, archive download, and file cleanup routines
Affected VersionsBackupSheep WordPress Plugin <= 1.8All deployed installations
Fixed VersionNone (Abandoned / Closed on WordPress.org)Immediate plugin removal required
Operational ImpactTotal WordPress CMS & Database CompromisePassword hash exfiltration, wp-config.php deletion, site hijacking

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.

<?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]);
}

Automated botnets and vulnerability scanners scan for the BackupSheep plugin footprint to execute multi-stage site compromises:

  1. Mass Discovery of Unconfigured Plugins: Attackers scan for endpoints matching /wp-json/backupsheep/v1/ or check wp-content/plugins/backupsheep/readme.txt to identify vulnerable targets.
  2. 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.
  3. Site Hijacking via wp-config.php Deletion: In instances where database password cracking is unfeasible, attackers call /wp-json/backupsheep/v1/delete with file_path=.../wp-config.php. Deleting wp-config.php forces 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.
  4. 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.

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-85cbe101148b
status: experimental
description: Detects HTTP requests directed to BackupSheep WordPress plugin REST API endpoints indicative of authentication bypass exploitation.
author: Hermes Codex Cyber Intelligence
date: 2026-10-01
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-101148
- https://patchstack.com/database
logsource:
category: webserver
product: wordpress
detection:
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_method
fields:
- c-ip
- cs-method
- cs-uri-stem
- sc-status
- cs-user-agent
falsepositives:
- Legitimate requests originating from confirmed BackupSheep cloud IP ranges with valid API keys
level: critical
tags:
- attack.initial_access
- attack.t1190
- attack.impact
- attack.t1485
- cve.2026.101148

  1. 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 --uninstall
    rm -rf wp-content/plugins/backupsheep/
  2. Audit Uploads and Purge Dangling Backup Archives:
    Inspect wp-content/uploads/ for lingering .sql or .zip archives generated by the plugin and delete them immediately to prevent public scraping.

  3. 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 in wp-config.php, update MySQL user permissions, and regenerate all authentication keys and salts in wp-config.php via https://api.wordpress.org/secret-key/1.1/salt/.

  4. Reset All WordPress Administrator Passwords:
    Force password resets for all users with administrator, editor, and shop_manager privileges to invalidate any cracked hashes.

  5. 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 endpoints
    location ~* /wp-json/backupsheep/ {
    return 403;
    }