CVE-2026-8095
HighCVSS 8.1Exploitation Probability (EPSS)
Low risk33th percentile - higher than 33% of all known CVEs
Summary
The Frontend File Manager Plugin for WordPress up to version 23.6 is vulnerable to authenticated arbitrary file deletion. The issue is a case-sensitive bypass of the wpfm_dir_path parameter sanitization in the wpfm_file_meta_update AJAX handler, allowing an attacker to delete arbitrary files on the server.
Risk Assessment
An authenticated attacker with Subscriber-level access can delete critical files like wp-config.php, potentially leading to full site takeover.
Recommendation
Immediately update the Frontend File Manager plugin to the latest available version that fixes this vulnerability.
Other vulnerabilities in Frontend File Manager Plugin
See all- CVE-2026-16292Medium
The Frontend File Manager Plugin for WordPress up to version 23.6 lacks nonce validation on one of its file-metadata update actions. This allows a CSRF attack where an attacker can modify the metadata of a logged-in user's uploaded file and then download it. When guest uploads are enabled, the same action is reachable unauthenticated against any user's file.
- CVE-2026-12277High
The Frontend File Manager Plugin for WordPress up to version 23.6 does not validate a file path derived from user input before deleting the referenced file, allowing unauthenticated users to delete arbitrary files on the server (such as wp-config.php) when guest upload mode is enabled. Deleting wp-config.php forces the site into its setup routine, which can be leveraged toward a full site takeover.
Original NVD description (English source)
The Frontend File Manager Plugin plugin for WordPress is vulnerable to Authenticated Arbitrary File Deletion in versions up to and including 23.6. This is due to a case-sensitive bypass of the wpfm_dir_path parameter sanitization in the wpfm_file_meta_update AJAX handler, where supplying WPFM_DIR_PATH in uppercase evades the unset check and is normalized to wpfm_dir_path by sanitize_key() during update_post_meta(), allowing an attacker to overwrite the stored file path with an arbitrary filesystem path that is then passed directly to unlink() in delete_file_locally() without any directory containment validation. This makes it possible for authenticated attackers with Subscriber-level access to delete arbitrary files on the server, including sensitive files such as wp-config.php, potentially leading to full site takeover.