dbcve.org
Frontend File ManagerWordPress extension · Najeebmedia

CVE-2024-25903

HIGH · 7.5 CVSS v3.1 Published 2024-03-17
Fix available
A fix is available. Upgrade to 22.8 or later.
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in N-Media Frontend File Manager.This issue affects Frontend File Manager: from n/a through 22.7.

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 · moderate confidence

An information disclosure vulnerability in N-Media Frontend File Manager plugin allows unauthorized actors to access sensitive data. The CVSS 7.5 score indicates network-exploitable access to sensitive information without authentication required. Version 22.7 and earlier versions are affected.

MitigationUpdate Frontend File Manager to the latest version beyond 22.7, or apply vendor-supplied patch if available. If immediate update is not possible, restrict access to the plugin's file handling endpoints via web server configuration.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Frontend File ManagerWordPress extension
Affected:< 22.8

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed Frontend File Manager version
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Frontend File Manager' by Najeebmedia, and note the version number displayed. Alternatively, check the plugin's main PHP file (typically wp-content/plugins/wp-file-manager or similar) for the 'Version' header in the plugin comments.
    Affected if The displayed version is 22.7 or any version number lower than 22.8
  2. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that Frontend File Manager shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if The plugin is active and the version is below 22.8
  3. Check for publicly accessible file handling endpoints
    Inspect your web server logs or use a web vulnerability scanner to identify exposed endpoints related to the file manager plugin. Common patterns include /wp-content/plugins/*/file-manager/* or similar paths. Test these endpoints via curl or browser without authentication.
    Affected if HTTP requests to file-related endpoints return sensitive data or directory listings without requiring login credentials
  4. Review file and directory permissions on upload folders
    Examine the permissions on wp-content/uploads and any custom upload directories configured for the plugin. Use ls -la command or file manager to verify directories are not world-readable or writable.
    Affected if Upload directories have permissions set to 777 or allow world-readable access to sensitive uploaded files

Your environment is affected if the Frontend File Manager plugin version is 22.7 or earlier AND the plugin is actively installed on your WordPress site.

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
Upgrade available Upgrade to 22.8 or later
Fixed in 22.8
Interim mitigation

Update Frontend File Manager to the latest version beyond 22.7, or apply vendor-supplied patch if available. If immediate update is not possible, restrict access to the plugin's file handling endpoints via web server configuration.

Recommended fix High confidence

22.8

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > All Plugins in your WordPress admin dashboard
  3. Locate Frontend File Manager plugin
  4. Update the plugin to version 22.8 or later
  5. Verify the update was successful by confirming the installed version shows 22.8 or higher

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

Fix this in Frontend File Manager 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 the upgrade done

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-2024-25903 — 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-2024-25903 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