CVE-2026-15991 json
File Manager 6.0 - 6.9 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Read and Deletion via 'cmd' Query Parameter
published 3mo ago modified 2mo ago also EUVD-2026-53703
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
The File Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the connector function in all versions from 6.0 - 6.9. This makes it possible for authenticated attackers, with subscriber-level access and above, to read and delete arbitrary files on the server, which can lead to remote code execution when the right file is deleted (such as wp-config.php). The bypass is triggered by passing cmd=rm or cmf=file in the URL query string of a POST request: elFinder's bind registration reads the command exclusively from $_POST and therefore never registers the rm.pre permission handler, while the dispatcher reads from the merged $_GET+$_POST superglobal and executes the rm or file command unchecked against a volume that defaults to ABSPATH.
Is CVE-2026-15991 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- bitpressadmin File Manager
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/a041f15c-0e30-459b-8df7-0465c0bc268a?source=cve
- plugins.trac.wordpress.org /browser/file-manager/tags/6.9/backend/app/Http/Controllers/FileManagerController.php#L34
- plugins.trac.wordpress.org /browser/file-manager/tags/6.9/vendor/studio-42/elfinder/php/elFinder.class.php#L802
- plugins.trac.wordpress.org /browser/file-manager/tags/6.9/vendor/studio-42/elfinder/php/elFinderConnector.class.php#L320
- plugins.trac.wordpress.org /browser/file-manager/tags/6.9/backend/app/Http/Controllers/FileManagerController.php#L32
- plugins.trac.wordpress.org /browser/file-manager/tags/6.9/backend/app/Providers/AccessControlProvider.php#L121
- plugins.trac.wordpress.org /browser/file-manager/tags/6.9/backend/hooks/ajax.php#L10
- plugins.trac.wordpress.org /changeset?old_path=%2Ffile-manager/tags/6.9&new_path=%2Ffile-manager/tags/6.9.1
- plugins.trac.wordpress.org /changeset/3632660/file-manager/trunk/backend/app/Http/Controllers/FileManagerController.php
Sources
- CVE List CVE-2026-15991
- NVD CVE-2026-15991
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.