Skip to main content
VulnerabilityPublished

CVE-2026-19708: File Manager (WordPress plugin) · Information Exposure

Affects File Manager (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.0.5 when convenient.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 10 Nov 2026.

What to do

Upgrade File Manager (WordPress plugin) to 8.0.5.

Affected software

ProductAffectedFixed in
File ManagerAffected
  • >=7.2.2 <8.0.5
Fixed in
  • 8.0.5

AI-suggested

Upgrade the File Manager plugin to version 8.0.5 or later, where this vulnerability is fixed. Servers should also ensure that .htaccess protections are properly applied to directories containing sensitive backup files to prevent unauthorized access. Since a fix is available in version 8.0.5, applying this official update is the recommended remediation.

Description

The File Manager WordPress plugin versions from 7.2.2 up to but not including 8.0.5 contain an information exposure vulnerability. Unauthenticated users can download database backup archives, which may be stored under a fixed filename. This can lead to exposure of sensitive data such as user email addresses and password hashes on servers that do not enforce .htaccess protections for the directory.

References

Community reviews

Loading reviews…