CVE-2020-25213
Published: November 3, 2021
Official Description
WordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.
CISA KEV Advisory
WordPress File Manager Plugin Remote Code Execution Vulnerability
WordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.
Apply updates per vendor instructions.
Risk Analysis
The WordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files. The very high EPSS score indicates a strong likelihood of exploitation, and its inclusion in CISA's KEV confirms active exploitation, making this a critical vulnerability.
This vulnerability is actively exploited in the wild, meaning that functional exploits are circulating and being used by threat actors. This flaw is remotely exploitable.
Update the WordPress File Manager plugin to the latest secure version immediately. Regularly review and update all plugins and themes on WordPress sites to prevent exploitation.
Technical Analysis
CVE-2020-25213 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2020-25213 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2020-25213 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1