Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-15991

8.8 · HIGH

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.

Published Aug 6, 2026CWE-862EPSS 1.07%

Overview

CVE-2026-15991 is a high-severity vulnerability. It was published on August 6, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refplugins.trac.wordpress.org/browser/file-manager/tags/6.9/backend/app/Http/Controllers/FileManagerController.php#L32Refplugins.trac.wordpress.org/browser/file-manager/tags/6.9/backend/app/Http/Controllers/FileManagerController.php#L34Refplugins.trac.wordpress.org/browser/file-manager/tags/6.9/backend/app/Providers/AccessControlProvider.php#L121Refplugins.trac.wordpress.org/browser/file-manager/tags/6.9/backend/hooks/ajax.php#L10Refplugins.trac.wordpress.org/browser/file-manager/tags/6.9/vendor/studio-42/elfinder/php/elFinder.class.php#L802Refplugins.trac.wordpress.org/browser/file-manager/tags/6.9/vendor/studio-42/elfinder/php/elFinderConnector.class.php#L320Refplugins.trac.wordpress.org/changeset/3632660/file-manager/trunk/backend/app/Http/Controllers/FileManagerController.phpRefplugins.trac.wordpress.org/changeset?old_path=%2Ffile-manager/tags/6.9&new_path=%2Ffile-manager/tags/6.9.1Refwww.wordfence.com/threat-intel/vulnerabilities/id/a041f15c-0e30-459b-8df7-0465c0bc268a?source=cve

How CyberStrike helps

Frequently asked questions

What is CVE-2026-15991?

CVE-2026-15991 is a high-severity vulnerability. It was published on August 6, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2026-15991?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-15991?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-15991?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-15991 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999