dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-7306

HIGH · 7.5 CVSS v3.1 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 unauthorized loss of data due to a missing capability check on the wpfm_delete_multiple_files() function in all versions up to, and including, 21.5. This makes it possible for unauthenticated attackers to delete arbitrary posts.

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 is vulnerable to an IDOR/authorization bypass in versions up to 21.5. The wpfm_delete_multiple_files() function lacks a capability check (e.g., current_user_can('delete_posts')), allowing unauthenticated attackers to send crafted requests that delete arbitrary posts/pages on the WordPress site.

MitigationUpdate the plugin to version 21.6 or later which includes proper capability validation. If no patched version is available, temporarily disable the plugin or implement WAF rules to block unauthorized delete operations.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Verify Frontend File Manager plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Frontend File Manager' or check the plugin files in wp-content/plugins/frontend-file-manager/ for a main PHP file containing the version header
    Affected if The plugin is present on the site
  2. Check the installed plugin version
    In WordPress admin, view the plugin details to see the version number, or open the main plugin PHP file (e.g., file-manager.php) and locate the Version: header in the plugin comment block
    Affected if The version is 21.5 or lower (any version up to and including 21.5)
  3. Confirm the vulnerable function exists
    Examine the main plugin PHP file for the function 'wpfm_delete_multiple_files' - search for 'function wpfm_delete_multiple_files' within the plugin directory
    Affected if The function exists in the code (present in versions up to 21.5)
  4. Check if the AJAX action is publicly registered
    Search the plugin code for 'add_action' hooks registering 'wpfm_delete_multiple_files' or similar AJAX endpoints - look for 'wp_ajax_wpfm_delete_multiple_files' or 'wp_ajax_nopriv_wpfm_delete_multiple_files' where nopriv allows unauthenticated access
    Affected if An AJAX action is registered without a capability check, allowing unauthenticated access

The site is affected if the Frontend File Manager plugin version 21.5 or lower is installed and the delete_multiple_files function is exposed without proper authorization checks.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 21.6 or later which includes proper capability validation. If no patched version is available, temporarily disable the plugin or implement WAF rules to block unauthorized delete operations.

Recommended fix Moderate confidence

Version 21.6 or later (latest available version recommended)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Frontend File Manager Plugin' (may be listed as 'WordPress File Manager' or similar)
  4. Check if an update is available for the plugin
  5. Update the plugin to the latest version (version 21.6 or later, which should contain the security fix)
  6. Verify the update was successful and the plugin is now running a version higher than 21.5

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7306 — 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-2023-7306 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