Skip to main content
Menu
CVEs

CVE

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.

CVE-2026-82025EUVD-2026-127006GHSA-3MM8-372G-RMPGNeeds attention

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

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

8.6HighCNA
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in 8.0.7
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. WP File Manager versions before 8.0.7 Misconfigured elFinder connector where an empty uploadDeny list causes allowPutMime() to return true

Published
Last modified
First public exploit on GitHub Nov 17
Last checked
39/100 · provisional
Specific setups only
1 proof of concept on GitHub

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.

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

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

“WP File Manager before 8.0.7 contains a file upload restriction bypass vulnerability”

vulncheck.com

cve.now Index

39Pcve.now Index 39 of 100 · methodology v3 · provisional
  • Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 46 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    WP File Manager versions before 8.0.7 Misconfigured elFinder connector where an empty uploadDeny list causes allowPutMime() to return true
  • Upgrade to a fixed version: 8.0.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Exploit code on GitHub

    rxsklife/CVE-2026-82025

Affected versions

  • mndpsingh287 WP File Manager

    fixed in 8.0.7

Evidence 5

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

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

  1. Exploit

Other links · 2

  1. Patch
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-82025

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: cve.now feed data

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: vulncheck.com

Which versions are affected by CVE-2026-82025?

WP File Manager: before 8.0.7.Source: cve.now feed data

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: vulncheck.com

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: vulncheck.com

More CVEs