Skip to main content

File Manager EUVDEUVD-2026-87530

| CVE-2026-19708 MEDIUM
Information Exposure (CWE-200)
2026-09-26 WPScan GHSA-w9qj-pq6f-hqr7
5.9
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running File Manager < 8.0.5
  2. Delivery
    Request backup archive at fixed/guessable path
  3. Exploit
    Server serves archive (no .htaccess enforcement)
  4. Execution
    Download full database dump
  5. Persist
    Crack exfiltrated password hashes offline
  6. Impact
    Take over user/admin accounts

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the File Manager WordPress plugin at version 7.2.2 through before 8.0.5, AND a web server that does NOT apply/honor the plugin directory's .htaccess protection (e.g., nginx, or Apache configured with AllowOverride off) - this is the primary gate, since compliant Apache setups block the download. It further depends on the backup archive existing and being reachable at a predictable/fixed filename (the description notes archives are 'in some cases' written under a fixed filename, aiding guessing). No authentication (PR:N) and no user interaction (UI:N) are needed, but the non-default-hosting precondition and the need for a backup to have been generated raise attack complexity (AC:H) and limit realistic exposure.

Impact

This is a confidentiality-only unauthenticated information-disclosure flaw (CWE-200) with a vendor CVSS of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), which I concur with. The signals are internally consistent and point to real-but-conditional risk rather than a top-tier emergency: PR:N/AV:N makes it remotely reachable without credentials, but AC:H correctly captures the two limiting conditions in the description - the backup archive must be at a predictable/fixed filename AND the web server must NOT be honoring the plugin directory's protective .htaccess (i.e., nginx, or Apache with AllowOverride off/misconfigured). EPSS is only 0.14% (3rd percentile) and SSVC records Exploitation:none, Automatable:no, Technical Impact:partial - so despite public POC code (WPScan) and an available patch, there is no evidence of active or automated exploitation. It is NOT in CISA KEV. The publicly available exploit code raises the practical risk above the low EPSS suggests, but the .htaccess-dependent gate keeps this from being universally exploitable. Net: a genuine but medium-tier issue - the C:H impact (full DB dump with every user's email and password hash, enabling offline cracking and account takeover) is serious wherever the .htaccess is not enforced, but the non-default-hosting precondition and low automability temper urgency. No conflicting signals; the low EPSS despite POC availability reflects targeted/manual rather than widespread exploitation.

Exploit ScenarioDerived

On a WordPress site running File Manager < 8.0.5 behind a web server that does not apply the plugin directory's .htaccess (e.g., nginx or Apache with AllowOverride disabled), an unauthenticated attacker requests the backup archive at its predictable/fixed path and downloads a complete database dump containing every user's email address and password hash. Public exploit code is available via WPScan, so no custom tooling is required; the attacker then cracks the hashes offline to compromise admin and user accounts.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 27, 2026

Unauthenticated information disclosure in the File Manager WordPress plugin (versions 7.2.2 through before 8.0.5) lets remote attackers download database backup archives that the plugin leaves reachable in its directory, leaking every user's email address and password hash. The flaw only lands on servers that do not honor the plugin directory's .htaccess protection - nginx hosts or Apache with AllowOverride disabled - and it also depends on a backup archive having been generated and being reachable at a predictable or fixed filename, which is why the vendor and the independent assessment both score it AC:H and confidentiality-only (CWE-200, CVSS 5.9). Publicly available exploit code exists per WPScan, but there is no confirmed active exploitation (CISA SSVC: Exploitation none) and EPSS is low at 0.14% (3rd percentile), so exposure is best modeled as a realistic targeted/lateral-movement risk on non-compliant web server configurations rather than a mass-exploitation event.

RemediationAI

Upgrade the File Manager WordPress plugin to 8.0.5 or later, which is the version boundary at which the affected range (7.2.2 through before 8.0.5) ends and a vendor patch is available; this is the primary and sufficient fix. If immediate upgrading is not possible, the highest-value compensating control is to stop relying on .htaccess: on nginx add a location block that returns 403 (or denies) for the plugin's backup directory and any .sql/.zip/.gz archive paths, and on Apache ensure AllowOverride All (or at least AllowOverride Limit/AuthConfig as needed) is set for the WordPress document root so the shipped .htaccess is actually evaluated - note that on nginx this rule must be maintained through plugin updates, and on Apache relaxing AllowOverride has a modest performance and configuration-governance cost. Additionally, delete or relocate existing backup archives out of the web root (or serve them via an authenticated endpoint), and consider adding a WAF/reverse-proxy rule blocking direct GETs to files matching backup-archive naming patterns; a WAF is only a partial control because fixed filenames and unknown backup paths can evade pattern-based rules. Because the leaked dump contains every user's email and password hash, treat any potentially exposed site as compromised: force a password reset for all users, rotate database and any credentials stored in the dump, and review access logs for requests to backup-looking paths before assuming no download occurred. Reference material: WPScan advisory https://wpscan.com/vulnerability/a0cbfd20-7741-44d0-96c4-054a7952f81b/ and NVD https://nvd.nist.gov/vuln/detail/CVE-2026-19708.

Affected VersionsENISA

File Manager 7.2.2 <8.0.5

Affected Packages

euvd file_manager fix: 8.0.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is a classic CWE-200 exposure of sensitive information to an unauthorized actor, rooted in the File Manager plugin's habit of placing its database backup archives inside a web-accessible directory and relying on Apache .htaccess rules to deny direct HTTP access. That defense is configuration-dependent: nginx ignores .htaccess entirely, and Apache only honors it when AllowOverride permits - so on those hosts the archives are simply downloadable by anyone who can guess or derive the path. The description notes that in some cases backups are written under a fixed, predictable filename, which lowers the guessing effort and turns what would otherwise be a path-discovery problem into a near-direct request. The exposed artifacts are full database dumps containing all user email addresses and password hashes, which is valuable both for credential cracking/reuse and for reconnaissance; however, the attack still requires the non-default server condition plus the prior existence of a generated backup, which is why the CVSS vector carries AC:H (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) rather than a lower complexity. The CPE record (cpe:2.3:a:unknown:file_manager:*) is generic and does not disambiguate the vendor or enumerate version constraints beyond the EUVD range, so version-based asset matching should be done from the plugin slug and installed version rather than CPE.

Know when File Manager gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 5.9 MEDIUM

Remote unauthenticated (AV:N/PR:N/UI:N) but gated by server not enforcing .htaccess plus predictable filename (AC:H); full DB dump gives C:H, no integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
CVSS changed
Sep 26, 2026 - 23:37 NVD
5.9 (None) 5.9 (MEDIUM)
Patch available
Sep 26, 2026 - 07:16 EUVD
CVE Published
Sep 26, 2026 - 06:00 cve.org
MEDIUM 5.9
CVE Published
Sep 26, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The File Manager WordPress plugin before 8.0.5 does not prevent unauthenticated users from downloading its database backup archives, and in some cases writes them under a fixed filename, allowing unauthenticated attackers to retrieve a full database dump including every user's email address and password hash on servers that do not apply the directory's .htaccess file.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
Popular WordPress file-management plugin, but exact vendor/plugin identity unconfirmed (vendor 'unknown')
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2020-25213 CRITICAL POC
9.8 Sep 09

The File Manager (wp-file-manager) plugin before 6.9 for WordPress allows remote attackers to upload and execute arbitra

CVE-2023-6846 HIGH POC
8.8 Feb 05

Remote code execution in the WordPress File Manager Pro plugin (versions up to and including 8.3.4) allows authenticated

CVE-2023-6825 CRITICAL POC
9.9 Mar 13

The File Manager and File Manager Pro plugins for WordPress are vulnerable to Directory Traversal in versions up to, and

CVE-2026-6382 CRITICAL POC
9.1 Jul 06

OS command injection in a family of popular WordPress file-manager plugins - FileOrganizer (before 1.1.9), Advanced File

CVE-2026-17540 HIGH POC
8.8 Aug 10

Missing authorization controls in the File Manager WordPress plugin before version 6.9.1 allow any authenticated user -

CVE-2026-85081 HIGH POC
7.5 Sep 26

Cross-site scripting in the WordPress File Manager plugin (below 8.0.5), FileOrganizer (below 1.2.1) and File Manager Pr

CVE-2026-17541 HIGH POC
7.5 Aug 10

Unauthenticated information disclosure in the File Manager WordPress plugin before 6.9.1 exposes a REST API route withou

CVE-2026-17542 HIGH POC
7.5 Aug 10

Missing capability checks in the File Manager WordPress plugin before version 6.9.1 expose the entire WordPress installa

CVE-2020-24312 HIGH POC
7.5 Aug 26

mndpsingh287 WP File Manager v6.4 and lower fails to restrict external access to the fm_backups directory with a .htacce

CVE-2023-5907 MEDIUM POC
6.5 Dec 11

The File Manager WordPress plugin before 6.3 does not restrict the file managers root directory, allowing an administrat

CVE-2024-1538 HIGH
8.8 Mar 21

The File Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including,

CVE-2021-24177 MEDIUM POC
5.4 Apr 05

In the default configuration of the File Manager WordPress plugin before 7.1, a Reflected XSS can occur on the endpoint

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy