How severe is CVE-2020-25213?

CVE-2020-25213 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2020-25213?

Affected package information for CVE-2020-25213 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2020-25213?

Apply the filemanagerpro file manager security patch or hotfix for CVE-2020-25213 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2020-25213 across my infrastructure?

Inventory every filemanagerpro file manager deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2020-25213 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2020-25213?

O3 detects and blocks CVE-2020-25213 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2020-25213 actively exploited in the wild?

Yes. There are 16 known exploit references for CVE-2020-25213, including 2 documented proof-of-concept exploits on Exploit-DB and 11 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-25213?

CVE-2020-25213 has an EPSS (Exploit Prediction Scoring System) score of 97.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2020-25213 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-25213 (WordPress File Manager Plugin Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2020-25213?

CVE-2020-25213 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2020-25213?

CVE-2020-25213 affects filemanagerpro file manager. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2020-25213?

A Nuclei detection template exists for CVE-2020-25213, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2020-25213, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-25213 published, and has it been updated?

CVE-2020-25213 was published on September 9, 2020 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2020-25213

CRITICAL

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…

Published

Sep 9, 2020

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

16 known

EPSS Exploitation Probability

via FIRST.org ↗

97.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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 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.

Affected Products

1 product · 1 configurations

Application

file managerfilemanagerpro

< 6.9

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-51224webappsphp✓ Verified

WP-file-manager v6.9 - Unauthenticated Arbitrary File Upload leading to RCE

by BLY · Apr 3, 2023

Exploit-DB Source

EDB-49178webappsphp

WordPress Plugin Wp-FileManager 6.8 - RCE

by Mansoor R · Dec 2, 2020

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every filemanagerpro file manager deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the filemanagerpro file manager security patch or hotfix for CVE-2020-25213 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2020-25213 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2020-25213. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2020-25213 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2020-25213 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works