Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-86826 Overview
CVE-2026-86826 affects the BackWPup WordPress plugin in versions prior to 5.7.7. The plugin fails to restrict web access to the working directory it uses during backup restores. On web servers that do not honour .htaccess rules, such as NGINX, unauthenticated attackers can download the full backup archive left behind by an interrupted restore. These archives contain database dumps and site files, including credentials and secret keys. The flaw is categorized under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Unauthenticated attackers can retrieve complete WordPress backup archives containing database dumps, credentials, and secret keys from affected NGINX-hosted sites.
Affected Products
- BackWPup WordPress plugin versions prior to 5.7.7
- WordPress sites running the plugin on NGINX or other web servers that do not process .htaccess directives
- Sites with interrupted restore operations that left artifacts in the plugin's working directory
Discovery Timeline
- 2026-10-08 - CVE-2026-86826 published to NVD
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-86826
Vulnerability Analysis
The BackWPup plugin uses a working directory on the WordPress filesystem to stage files during backup and restore operations. The plugin ships with an .htaccess file intended to deny HTTP access to that directory. Apache honours those directives, but NGINX and similar servers ignore .htaccess entirely. When a restore operation is interrupted, the extracted backup archive remains in that directory and becomes directly reachable over HTTP.
The exposed archive typically contains a full MySQL dump and the complete WordPress file tree. Attackers who retrieve it gain WordPress administrator password hashes, wp-config.php secrets, database credentials, and any API keys stored in the configuration. The EPSS score of 0.216% reflects limited current exploitation activity, but the data recovered enables full site takeover.
Root Cause
The plugin relies solely on .htaccess to enforce access control over its working directory. This control is server-specific and does not apply to NGINX, LiteSpeed in some configurations, or any environment where Apache override files are not processed. The plugin additionally fails to clean up backup artifacts when a restore terminates abnormally.
Attack Vector
An unauthenticated remote attacker enumerates the known BackWPup working directory path on a target WordPress site. If a prior restore was interrupted, the backup archive remains at a predictable URL. The attacker issues a direct HTTP GET request to download the archive. No authentication, user interaction, or elevated privileges are required. Exploitation is conditional on the server ignoring .htaccess and on a residual archive being present, which raises attack complexity.
See the WPScan Vulnerability Report for additional technical detail.
Detection Methods for CVE-2026-86826
Indicators of Compromise
- HTTP GET requests from external sources targeting the BackWPup working directory path under wp-content/uploads/
- Successful HTTP 200 responses serving .zip, .tar, or .sql files from the plugin's working directory
- Unexpected archive files remaining in the BackWPup working directory after a restore operation
- Outbound requests referencing enumerated backup file names from unknown IP addresses
Detection Strategies
- Review NGINX and reverse proxy access logs for requests to BackWPup working directory paths and flag any that return archive content types
- Correlate interrupted restore events in the WordPress admin log with subsequent external access to the working directory
- Scan the filesystem for stale backup archives inside the plugin working directory outside active restore windows
Monitoring Recommendations
- Alert on HTTP responses larger than a defined threshold served from wp-content paths associated with backup plugins
- Monitor for repeated 404 responses that indicate directory enumeration against known backup plugin paths
- Track BackWPup plugin version across managed WordPress installations and surface instances below 5.7.7
How to Mitigate CVE-2026-86826
Immediate Actions Required
- Upgrade BackWPup to version 5.7.7 or later on all WordPress installations
- Manually delete any residual files in the BackWPup working directory after confirming no restore is in progress
- Rotate WordPress secret keys in wp-config.php, database credentials, and any API keys that may have been exposed
- Audit web server access logs for prior unauthorized downloads of backup archives
Patch Information
The vendor addressed the issue in BackWPup 5.7.7. The fix restricts web access to the working directory at the application and server level rather than relying solely on .htaccess. Refer to the WPScan Vulnerability Report for vendor patch references.
Workarounds
- Add an explicit NGINX location block that returns 403 for requests targeting the BackWPup working directory
- Move the plugin working directory outside the web-accessible document root where supported
- Enforce HTTP authentication at the web server level on wp-content/uploads/backwpup-* paths until patching is complete
# NGINX configuration example to block access to BackWPup working directory
location ~* /wp-content/uploads/backwpup-.*/ {
deny all;
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

