# CVE-2020-25213: WordPress File Manager Plugin Remote Code Execution

> Remote attackers can upload and execute arbitrary PHP code via the wp-file-manager plugin, leading to full site compromise.

- **Severity:** Critical 10.0 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-w774-7g7w-83fx

## What is CVE-2020-25213?

CVE-2020-25213 is a critical vulnerability in n/a, published on 9 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2020-25213?

It affects 1 product.


Products: Filemanagerpro File Manager.

## How do I fix CVE-2020-25213?

No fix has been published for CVE-2020-25213 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-25213 being exploited?

Yes. Attackers have exploited CVE-2020-25213 in the wild since at least 3 Nov 2021.

Public exploit code:

- https://medium.com/@mansoorr/exploiting-cve-2020-25213-wp-file-manager-wordpress-plugin-6-9-3f79241f0cd8 (github_poc): https://github.com/mansoorr123/wp-file-manager-CVE-2020-25213
- Python exploit for RCE in Wordpress (github_poc): https://github.com/BLY-Coder/Python-exploit-CVE-2020-25213
- Python Interactive Exploit for WP File Manager Vulnerability. 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. (github_poc): https://github.com/E1tex/Python-CVE-2020-25213
- Exploit para explotar la vulnerabilidad CVE-2020-25213 en WPFileManager < 6.9 (github_poc): https://github.com/Maalfer/CVE-2020-25213-exploit
- CVE-2020-25213 Wordpress File Manager 6.7 Plugin 0day exploit (github_poc): https://github.com/kakamband/WPKiller
- WordPress File Manager Unauthenticated Remote Code Execution (metasploit)

## Other vulnerabilities in n/a

- [CVE-2018-25105](https://insights.sbomify.com/CVE-2018-25105/): File Manager <= 3.0 - Unauthenticated Arbitrary File Upload/Download (critical 9.8)
- [CVE-2024-8507](https://insights.sbomify.com/CVE-2024-8507/): File Manager Pro <= 8.3.9 - Cross-Site Request Forgery to Arbitrary File Upload (high 8.8)
- [CVE-2024-1538](https://insights.sbomify.com/CVE-2024-1538/): File Manager <= 7.2.4 - Cross-Site Request Forgery to Local JS File Inclusion (high 8.8)
- [CVE-2023-6846](https://insights.sbomify.com/CVE-2023-6846/): File Manager Pro <= 8.3.4 - Authenticated (Subscriber+) Arbitrary File Upload (high 8.8)
- [CVE-2018-16966](https://insights.sbomify.com/CVE-2018-16966/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25213 and fix it if it is affected.

What it is: CVE-2020-25213 is a critical vulnerability in n/a, published on 9 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-25213 in the wild since at least 3 Nov 2021.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25213/ (Markdown: https://insights.sbomify.com/CVE-2020-25213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25213
- OSV: https://osv.dev/vulnerability/CVE-2020-25213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25213/
Summaries are generated and may contain mistakes; the official description above is the record.