dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-5337

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
During the analysis, it was identified that authenticated attackers with Subscriber-level access or higher are able to perform an Insecure Direct Object Reference (IDOR) attack. This vulnerability exists because the Frontend File Manager Plugin WordPress plugin through 23.6 does not properly validate user authorization for the requested uploaded file when processing download requests. By modifying the value of the 'file_id' parameter in the download endpoint (e.g., http://localhost/?do=wpfm_download&file_id=40&nm_file_nonce=a36fb893f1), an attacker can access files belonging to other users, including privileged users such as administrators. This allows unauthorized access/read to sensitive data stored within the application.

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 WordPress plugin (versions up to 23.6) contains an IDOR vulnerability in its file download functionality. Authenticated users with Subscriber-level access or higher can manipulate the 'file_id' parameter in the download endpoint (e.g., ?do=wpfm_download&file_id=40&nm_file_nonce=...) to access files belonging to other users, including administrators. The plugin fails to validate that the requesting user has authorization to access the specific file before serving it.

MitigationUpdate to a patched version of the Frontend File Manager plugin that implements proper user authorization validation for file download requests, ensuring the current user owns or has permission to access the requested file_id.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Frontend File Manager' or check the /wp-content/plugins/ directory for the plugin folder
    Affected if The plugin is present in the installation
  2. Determine the installed plugin version
    In WordPress admin_plugins list view, the version number is displayed next to the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/frontend-file-manager/ for the 'Version' tag
    Affected if Version is 23.6 or lower, or if the version cannot be determined (older unmaintained version)
  3. Confirm authenticated user access exists
    Check WordPress user roles under Users > All Users. Look for any role at Subscriber level or higher (Subscriber, Contributor, Author, Editor, Administrator)
    Affected if At least one user with Subscriber-level access or higher exists in the system
  4. Verify the download endpoint is accessible
    Test access to a URL pattern containing '?do=wpfm_download&file_id=' on the site. This endpoint should exist and accept file_id parameters for the vulnerability to be exploitable
    Affected if The download endpoint responds and accepts file_id parameters without proper ownership validation

If the Frontend File Manager plugin versions 23.6 or lower is installed AND at least one authenticated user with Subscriber-level access exists, the IDOR vulnerability is present and exploitable in the environment.

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 to a patched version of the Frontend File Manager plugin that implements proper user authorization validation for file download requests, ensuring the current user owns or has permission to access the requested file_id.

Recommended fix Moderate confidence

Latest version of Frontend File Manager plugin (version 23.7 or higher)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Frontend File Manager' plugin in the list
  4. 4. Check the current installed version number
  5. 5. If the installed version is 23.6 or lower, update the plugin to the latest available version
  6. 6. After updating, verify the fix by confirming that file download requests properly validate ownership

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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