CVE-2024-1538: File Manager (WordPress plugin) · Cross-Site Request Forgery (CSRF)
Affects File Manager (WordPress plugin)Source CVE Database V5
Not known to be exploited · 10% EPSS · CVSS 8.8 High · fixed in 7.2.4 : patch File Manager (WordPress plugin) soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 10.6% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.2.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mndpsingh287 File Manager | Affected
| Fixed in– |
AI-suggested
Upgrade the File Manager plugin to version 7.2.5 or later, where the vulnerability is fully patched. Versions up to and including 7.2.4 are vulnerable, with only a partial fix applied in 7.2.4. No other mitigations are indicated by the vendor advisory.
Description
The File Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.2.4. This is due to missing or incorrect nonce validation on the wp_file_manager page that includes files through the 'lang' parameter. This makes it possible for unauthenticated attackers to include local JavaScript files that can be leveraged to achieve RCE via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This issue was partially patched in version 7.2.4, and fully patched in 7.2.5.