Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
6DescriptionCVE.org
During the analysis, it was identified that authenticated attackers with Subscriber-level access or higher are able to perform an Insecure Direct Object Reference (IDOR) attack. This vulnerability exists because the Frontend File Manager Plugin WordPress plugin through 23.6 does not properly validate user authorization for the requested uploaded file when processing download requests. By modifying the value of the 'file_id' parameter in the download endpoint (e.g., http://localhost/?do=wpfm_download&file_id=40&nm_file_nonce=a36fb893f1), an attacker can access files belonging to other users, including privileged users such as administrators. This allows unauthorized access/read to sensitive data stored within the application.
AnalysisAI
Frontend File Manager Plugin for WordPress through version 23.6 allows authenticated Subscriber-level users and higher to read arbitrary files belonging to other users via insecure direct object reference (IDOR) in the download endpoint. By manipulating the 'file_id' parameter, attackers can bypass authorization checks and access sensitive data stored by administrators and other privileged users. Publicly available exploit code exists for this vulnerability, though EPSS scoring (0.02%) suggests limited real-world exploitation relative to its high CVSS rating.
Technical ContextAI
The vulnerability resides in the Frontend File Manager Plugin's file download handler, which processes requests through the 'wpfm_download' action parameter. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), where the plugin fails to validate that the requesting user has legitimate access to the file identified by the 'file_id' parameter before serving the download. The nonce check ('nm_file_nonce') provides CSRF protection but does not enforce per-file authorization. This is a classic IDOR flaw where sequential or enumerable identifiers are exposed in the URL without proper access control validation, allowing horizontal privilege escalation from Subscriber to access administrative files.
RemediationAI
Update Frontend File Manager Plugin to a version after 23.6 immediately. If an update is not yet available from the plugin vendor, disable the download functionality or restrict access to the 'wpfm_download' endpoint via .htaccess or web application firewall rules (e.g., deny requests to '?do=wpfm_download' for non-administrator users). WordPress administrators should verify that file permissions are correctly configured and audit recent file downloads for unauthorized access. As a temporary compensating control, restrict user registration if the site does not require open sign-ups, reducing the number of attackers capable of obtaining Subscriber credentials. Monitor access logs for enumeration patterns (sequential file_id requests) and implement per-user file access logging in the plugin settings if available.
More in Frontend File Manager Plugin
View allThe Frontend File Manager plugin for WordPress is vulnerable to Authenticated Settings Change in versions up to, and inc
The Frontend File Manager plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Download in versions up t
Unauthenticated file disclosure in the Frontend File Manager Plugin for WordPress (all versions through 23.6) exposes ev
The Frontend File Manager plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in versions
The Frontend File Manager plugin for WordPress is vulnerable to Unauthenticated HTML Injection in versions up to, and in
Permanent deletion of arbitrary WordPress posts and pages is possible via the Frontend File Manager Plugin (all versions
The Frontend File Manager plugin for WordPress is vulnerable to Unauthenticated Arbitrary Post Deletion in versions up t
The Frontend File Manager Plugin WordPress plugin before 22.6 has a vulnerability that allows an Editor+ user to bypass
The Frontend File Manager plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 1
The Frontend File Manager plugin for WordPress is vulnerable to Unauthenticated Post Meta Change in versions up to, and
The Frontend File Manager plugin for WordPress is vulnerable to Unauthenticated Content Injection in versions up to, and
Stored Cross-Site Scripting in the Frontend File Manager Plugin for WordPress (versions through 23.6) allows any authent
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-26818