The Backup Migration WordPress plugin before 2.0.0 does not properly generate its backup path in certain server
Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium.
Data as of 16 Nov 2026, 01:28 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.9 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
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 15 Nov 2026.
What to do
AI-suggested
Until a fix is available, restrict access to backup and log files via server configuration to prevent unauthorized downloads.
Description
The Backup Migration WordPress plugin versions before 2.0.0 have a vulnerability where the backup path is improperly generated under certain server configurations. This flaw allows unauthenticated users to access a log file that reveals the backup filename, which can then be downloaded without authentication.