dbcve.org
CWE-73Weakness · CWE-73

CVE-2026-8095

HIGH · 8.1 CVSS v3.1 Published 2026-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Frontend File Manager Plugin for WordPress versions up to 23.6 contains an authenticated arbitrary file deletion vulnerability in the wpfm_file_meta_update AJAX handler. The vulnerability stems from a case-sensitive bypass where supplying the WPFM_DIR_PATH parameter in uppercase evades an unset check, and sanitize_key() normalizes it to wpfm_dir_path during update_post_meta(). This allows authenticated subscribers 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, enabling deletion of sensitive files like wp-config.php.

MitigationImplement case-insensitive parameter handling and add strict directory containment validation ensuring the file path resolves within the designated upload directory before passing to unlink(). Consider implementing an allowlist of permitted files/directories and adding capability checks for the AJAX handler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WordPress installation exists
    Check for the presence of wp-config.php in the web root directory
    Affected if WordPress is installed and the plugin could be present
  2. Identify Frontend File Manager Plugin installation
    Check for the plugin directory at /wp-content/plugins/frontend-file-manager/ or search for 'Frontend File Manager' in the WordPress plugins database table
    Affected if The plugin is installed on the WordPress site
  3. Verify plugin version
    Inspect the plugin main file (typically plugin-name.php) for the 'Version' header, or query the wp_options table for the option_name containing 'active_plugins' and the plugin version
    Affected if The installed version is 23.6 or lower (any version up to and including 23.6)
  4. Confirm AJAX handler is accessible to low-privilege users
    Check the wp_usermeta table for subscriber-level users and inspect the plugin code for add_action('wp_ajax_wpfm_file_meta_update', ...) calls without capability checks like 'manage_options'
    Affected if The wpfm_file_meta_update AJAX action is registered without restricting to administrators or the delete_file_locally() function can be reached by subscriber-level accounts
  5. Verify unlink call lacks directory containment validation
    Examine the delete_file_locally() function in the plugin source code to confirm that the file path passed to unlink() is not validated against the upload directory using realpath() or similar containment checks
    Affected if The unlink() call in delete_file_locally() receives the path directly from user-controlled input without validating it stays within the allowed upload directory

A user is affected if the Frontend File Manager Plugin version 23.6 or lower is installed, the wpfm_file_meta_update AJAX handler is accessible to subscriber-level accounts, and the delete_file_locally() function does not validate that the file path to be deleted is contained within the designated upload directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement case-insensitive parameter handling and add strict directory containment validation ensuring the file path resolves within the designated upload directory before passing to unlink(). Consider implementing an allowlist of permitted files/directories and adding capability checks for the AJAX handler.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8095 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data