Description
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.
Published: 2026-06-27
Score: 8.1 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Frontend File Manager Plugin for WordPress is vulnerable to authenticated arbitrary file deletion in all releases up to version 23.6. The flaw arises from a case‑sensitive bypass in the wpfm_file_meta_update AJAX handler: an attacker can supply an uppercase WPFM_DIR_PATH value that bypasses the unset check, causing the plugin to overwrite the stored file path with an attacker‑controlled filesystem path. That path is later used directly by unlink() in delete_file_locally() without any containment validation, enabling the deletion of any file on the server. Consequently, a user with Subscriber or higher privileges can erase critical files such as wp‑config.php, potentially leading to complete site compromise.

Affected Systems

Vendors and products affected are nmedia:Frontend File Manager Plugin for WordPress, versions 23.6 and earlier. Any WordPress site that has installed this plugin and has users with Subscriber or higher roles is susceptible. The vulnerability exists regardless of the overall WordPress version or hosting environment, as the flaw is confined to the plugin’s internal file‑management routines.

Risk and Exploitability

With a CVSS score of 8.1, the vulnerability is classified as High severity. No EPSS score is available, and the vulnerability is not listed in CISA’s KEV catalog, but the lack of publicly known exploits combined with the severity suggests a moderate likelihood of exploitation. The assault vector is authenticated, relying on legitimate Subscriber access to the plugin’s AJAX endpoint (wpfm_file_meta_update). An attacker must first log into the WordPress site with a Subscriber role, then craft a request that exploits the sanitization bypass to direct unlink() at an arbitrary path; success leads to deletion of arbitrary server files.

Generated by OpenCVE AI on June 28, 2026 at 00:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest version of the Frontend File Manager Plugin that fixes the sanitization oversight.
  • If the patch cannot be applied immediately, revoke or disable the file‑manager feature for Subscriber members and limit file deletion capabilities to Administrators only.
  • Secure critical configuration files such as wp‑config.php by setting restrictive file permissions and, if possible, applying server‑level access controls.
  • Enable and review audit logging for file deletion attempts to detect and investigate suspicious activity.

Generated by OpenCVE AI on June 28, 2026 at 00:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 27 Jun 2026 23:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Frontend File Manager Plugin <= 23.6 - Authenticated (Subscriber+) Arbitrary File Deletion
Weaknesses CWE-73
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-06-27T23:28:36.879Z

Reserved: 2026-05-07T12:47:14.946Z

Link: CVE-2026-8095

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-28T00:30:04Z

Weaknesses
  • CWE-73

    External Control of File Name or Path