CVE-2020-25213
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.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H- packetstormsecurity.com/files/160003/WordPress-File-Manager-6.8-Remote-Code-Execution.htmlExploitThird Party Advisory
- packetstormsecurity.com/files/171650/WordPress-File-Manager-6.9-Shell-Upload.htmlExploitThird Party Advisory
- github.com/w4fz5uck5/wp-file-manager-0dayExploitThird Party Advisory
- hotforsecurity.bitdefender.com/blog/wordpress-websites-attacked-via-file-manager-plugin-vulnerability-24048.htmlBroken LinkThird Party Advisory
- plugins.trac.wordpress.org/changeset/2373068Patch
- seravo.com/blog/0-day-vulnerability-in-wp-file-manager/ExploitThird Party Advisory
- wordfence.com/blog/2020/09/700000-wordpress-users-affected-by-zero-day-vulnerability-in-file-manager-plugin/ExploitThird Party Advisory
- wordpress.org/plugins/wp-file-manager/ProductRelease Notes
- zdnet.com/article/millions-of-wordpress-sites-are-being-probed-attacked-with-recent-plugin-bug/Press/Media Coverage
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-25213US Government Resource
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1638 days
- CVSS
- 10.0 CRITICAL
- EPSS (30-day exploit probability)
- 97.3% · top 1% of all CVEs
- Weakness
- CWE-434
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.