CVE-2026-104307: BackUpWordPress (WordPress plugin) · External Control of File Name or Path
Affects BackUpWordPress (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 3.15 soon.
Data as of 8 Nov 2026, 07:04 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.15
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade BackUpWordPress (WordPress plugin) to 3.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BackUpWordPress | Affected
| Fixed in
|
AI-suggested
Upgrade the BackUpWordPress plugin to version 3.15 or later, where this vulnerability is fixed. If you cannot patch yet, restrict authenticated user roles to trusted individuals only, as any Subscriber or higher can exploit this flaw. No other vendor advisory mitigation is provided.
Description
BackUpWordPress plugin versions before 3.15 contain a vulnerability where an AJAX action that cleans up the backup directory lacks proper capability or nonce checks. This flaw allows any authenticated user with Subscriber or higher privileges to delete backup protection and working files, potentially disrupting backups and removing download protection from stored backups.