JetBackup Plugin Symlink Flaw Lets Admins Write Files Outside Backup Dir
CVE-2026-104068 allows authenticated WordPress admins to write arbitrary files via symlink abuse during backup restores in JetBackup versions before 3.1.24.10.
Key points
- The National Vulnerability Database rates CVE-2026-104068 as high severity with a CVSS score of 8.6.
- The flaw exists in the JetBackup plugin for WordPress in all versions prior to 3.1.24.10.
- Attackers can exploit this by crafting backup archives containing symbolic links that bypass destination containment checks.
The JetBackup plugin for WordPress contains a high-severity vulnerability that allows authenticated administrators to write files to unintended locations on the server. This flaw arises from improper handling of symbolic links during the backup import and restore processes, potentially leading to remote code execution depending on server configuration.
What happened
The National Vulnerability Database records CVE-2026-104068 as a high-severity issue affecting the JetBackup plugin for WordPress. The vulnerability is present in all plugin versions released before 3.1.24.10. It stems from a symlink-based arbitrary file write weakness, classified under CWE-59. During the backup import and restore operations, the plugin fails to validate symbolic link targets or enforce destination containment. An attacker who has gained access to an administrator account can craft a malicious backup archive.
This archive contains symbolic links that the extraction process follows without restriction. Consequently, the system writes attacker-controlled file contents outside the intended restore destination. The specific impact depends on the writable permissions of the destination directory and the underlying server configuration. This could potentially lead to server-side code execution if the attacker writes executable code to a web-accessible or script-interpreted directory.
Why it matters
Security operations teams must recognize that this vulnerability requires an authenticated administrator account, which changes the threat model compared to unauthenticated remote code execution flaws. However, the ability to write arbitrary files outside the expected directory structure is a significant escalation path. If an attacker compromises an admin account through phishing or credential stuffing, they can leverage this flaw to establish persistence or execute commands.
The risk is particularly acute for managed WordPress hosting environments where administrators frequently restore backups. The lack of validation on symbolic links means the plugin trusts the archive contents implicitly. This trust boundary violation allows data to escape the sandboxed restore area. While the initial access requirement limits the attack surface, the potential for full server compromise remains high. Teams should treat any admin account compromise as a critical incident that could lead to this specific exploitation vector.
Our take on the response
- Verify the current version of the JetBackup plugin on all managed WordPress installations.
- Ensure no versions prior to 3.1.24.10 are running in production or staging environments.
- Review recent backup restore logs for any anomalous file writes outside standard directories.
- Confirm that symbolic link following is restricted at the server or application level if possible.
What defenders should look for
Teams usually detect this activity by monitoring for unexpected file creation events during backup restoration windows. Check whether backup import jobs generate files in directories outside the standard WordPress content or upload folders. Look for alert triggers associated with symbolic link resolution failures or permission denied errors in system logs. Examine web server access logs for requests to newly created files that do not match known plugin assets.
Investigate any sudden changes to file ownership or permissions in sensitive system directories. Review administrator session logs for unusual backup restore actions, especially those involving large or unfamiliar archive sources. Monitor for outbound connections from the web server that might indicate a new command and control channel established via the written file.
What to do and how to stay safe: JetBackup
- Audit all WordPress installations to identify any running JetBackup versions older than 3.1.24.10.
- Restrict administrative access to backup restoration features to authorized personnel only.
- Monitor file system integrity for unexpected changes in directories outside the web root.
- Review server configurations to ensure symbolic links cannot traverse to sensitive system paths.
Step-by-step guide: Vulnerability Management Myths That Waste Your Time and Budget
General security guidance from the NetSec Tribune newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the severity rating for CVE-2026-104068?
The National Vulnerability Database rates CVE-2026-104068 as high severity with a CVSS score of 8.6.
Which versions of JetBackup are affected by this vulnerability?
All versions of the JetBackup plugin for WordPress before 3.1.24.10 are affected by this symlink-based arbitrary file write flaw.
What type of access is required to exploit this vulnerability?
An attacker requires an authenticated WordPress administrator account to craft and import a malicious backup archive containing symbolic links.




