CVE-2020-25213
Filemanagerpro File Manager ≤ 6.9
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2020-25213 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Filemanagerpro File Manager. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The File Manager (wp-file-manager) plugin before version 6.9 for WordPress contains an arbitrary file upload vulnerability tracked as CVE-2020-25213. The root cause is the plugin's renaming of an unsafe example elFinder connector file to a .php extension, which enables use of elFinder commands such as upload, mkfile, and put to write attacker-controlled PHP code into the wp-content/plugins/wp-file-manager/lib/files/ directory. The issue is classified under CWE-434 and carries a CVSS 3.1 base score of 10.0.
Unauthenticated remote attackers can exploit the flaw over the network to upload and execute arbitrary PHP, resulting in full compromise of confidentiality, integrity, and availability with scope change to other WordPress components. Public exploit code and Metasploit modules have been available since shortly after disclosure, lowering the barrier for mass compromise of unpatched sites.
The official mitigation is to update the plugin to version 6.9 or later, as reflected in the WordPress plugin repository changeset 2373068 that removed the vulnerable connector file. Multiple public advisories and proof-of-concept reports emphasize that sites remaining on earlier releases remain exposed until the update is applied.
The vulnerability saw active exploitation in the wild during August and September 2020, with observed campaigns leveraging it for website defacement and further malware deployment.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-17903
Vulnerability Data
The File Manager (wp-file-manager) plugin before 6.9 for WordPress allows remote attackers to upload and execute arbitrary PHP code because it renames an unsafe example elFinder connector file to have the .php extension. This, for example, allows attackers to run…
more
the elFinder upload (or mkfile and put) command to write PHP code into the wp-content/plugins/wp-file-manager/lib/files/ directory. This was exploited in the wild in August and September 2020.
- CWE(s)
- KEV Date Added
- 03 November 2021
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring identifiable owners for portable devices reduces the attack surface for unrestricted uploads of dangerous file types via anonymous media.
Dangerous file uploads can be detonated in the chamber to determine malice before any production write or execution occurs.
Prevents unrestricted writing of arbitrary or malicious firmware by keeping hardware write-protect enabled except under tightly controlled manual procedures.
Scans files from external sources on download/open/execute, blocking unrestricted uploads of dangerous file types.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.