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-86828 Overview
CVE-2026-86828 affects the BackWPup WordPress plugin in versions before 5.7.7. The plugin fails to properly restrict the destination path of files extracted during a backup restore operation when its fallback archive library is used. High-privileged users can write files outside the intended restore directory, potentially leading to remote code execution.
The flaw is categorized as a path traversal weakness ([CWE-22]). It affects WordPress sites that use BackWPup for backup and restoration workflows. Exploitation requires authentication at a high privilege level, which limits the attack surface but does not eliminate risk from compromised administrator accounts or malicious insiders.
Critical Impact
Successful exploitation allows an authenticated attacker to write arbitrary files to locations outside the restore directory, enabling PHP file deployment and remote code execution on the WordPress host.
Affected Products
- BackWPup WordPress plugin versions prior to 5.7.7
- WordPress installations using the plugin's fallback archive library during restore
- Sites where high-privileged accounts are available to attackers
Discovery Timeline
- 2026-10-08 - CVE-2026-86828 published to NVD
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-86828
Vulnerability Analysis
The vulnerability resides in the restore workflow of BackWPup, specifically when the plugin falls back to its secondary archive library for extracting backup contents. During extraction, the plugin does not validate that resolved file paths remain within the intended restore directory.
An attacker with a privileged account can craft a backup archive containing entries with traversal sequences in their path names. When the plugin processes these entries, it writes the files to attacker-controlled locations on the server. Placing a PHP file under the web root yields remote code execution via a subsequent HTTP request.
The weakness maps to [CWE-22] Improper Limitation of a Pathname to a Restricted Directory. Network-based exploitation is possible, but high privileges and attack complexity reduce the practical risk compared to unauthenticated flaws.
Root Cause
The fallback archive extraction routine lacks canonicalization and containment checks on archive member paths. Traversal segments such as ../ in archive entries are honored by the file writer, causing extraction outside the designated restore directory.
Attack Vector
Exploitation requires an authenticated session with high privileges, typically an administrator capable of initiating a restore. The attacker supplies or uploads a malicious backup archive and triggers the restore flow that invokes the fallback library. The crafted archive includes entries whose names traverse the directory structure, placing PHP payloads inside web-accessible paths.
See the WPScan Vulnerability Advisory for technical details on the vulnerable code path.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-86828
Indicators of Compromise
- Unexpected .php files appearing in web-accessible directories after a BackWPup restore operation
- Backup archives containing entries with ../ traversal sequences in their file names
- Modifications to WordPress core, theme, or plugin files outside the intended restore directory
- Web server logs showing requests to newly created, previously unknown PHP endpoints
Detection Strategies
- Inspect backup archives before restore for member paths containing traversal sequences or absolute paths
- Monitor filesystem write events originating from the PHP process during restore operations
- Compare post-restore filesystem state against expected restore directory contents and flag writes outside that boundary
Monitoring Recommendations
- Alert on BackWPup restore events initiated by administrator accounts and correlate with file creation events on the host
- Track WordPress administrator logins from unusual IPs and tie them to backup or restore plugin actions
- Enable PHP file integrity monitoring across the WordPress installation directory
How to Mitigate CVE-2026-86828
Immediate Actions Required
- Upgrade the BackWPup plugin to version 5.7.7 or later on all WordPress sites
- Audit administrator and high-privileged WordPress accounts and remove any that are unnecessary
- Review recent restore operations for signs of exploitation and inspect the filesystem for unexpected PHP files
Patch Information
The vendor addressed the issue in BackWPup version 5.7.7. The patched release enforces proper path validation during fallback archive extraction. Refer to the WPScan Vulnerability Advisory for the official fix reference.
Workarounds
- Restrict access to the WordPress administrator role and enforce multi-factor authentication for all privileged accounts
- Disable the BackWPup plugin until the upgrade to 5.7.7 can be completed
- Only restore backup archives from trusted, verified sources and reject archives from untrusted origin
- Apply filesystem-level permissions that prevent the PHP process from writing to directories outside the designated restore path
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

