dbcve.org
File ManagerWordPress extension · Filemanagerpro

CVE-2024-8507

HIGH · 8.8 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to 8.3.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 File Manager Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 8.3.9. This is due to missing or incorrect nonce validation on the 'mk_file_folder_manager' ajax action. This makes it possible for unauthenticated attackers to upload arbitrary files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 File Manager Pro WordPress plugin lacks nonce validation on the mk_file_folder_manager AJAX action, allowing unauthenticated attackers to forge requests that upload arbitrary files by tricking authenticated administrators into clicking malicious links.

MitigationUpdate the plugin to version 8.3.10 or later which includes proper nonce validation; until then, administrators should avoid clicking untrusted links while logged in.

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
File ManagerWordPress extension
Affected:< 8.3.10

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 the Filemanagerpro File Manager plugin is installed
    Log in to WordPress admin and go to Plugins > Installed Plugins, or check the wp-content/plugins/ directory for folders containing 'file-manager' or 'filemanagerpro'
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin Plugins page, find the 'Filemanagerpro File Manager' plugin and note the version number displayed; alternatively, read the main plugin PHP file header for 'Version:'
    Affected if The version number is less than 8.3.10
  3. Verify the vulnerable AJAX endpoint exists and is reachable
    Check if the file wp-admin/admin-ajax.php responds to action=mk_file_folder_manager (the plugin must be active for this to be functional)
    Affected if The endpoint responds and the plugin version is below 8.3.10
  4. Inspect plugin source for missing nonce validation
    Examine the PHP file handling the mk_file_folder_manager AJAX action (typically in the plugin's main directory) and look for wp_verify_nonce or check_admin_referer calls before file upload logic
    Affected if No nonce validation is found in the AJAX handler code and version is below 8.3.10

The environment is affected if the Filemanagerpro File Manager plugin is installed with a version lower than 8.3.10 and the mk_file_folder_manager AJAX action is accessible without nonce verification.

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 8.3.10 or later
Fixed in 8.3.10
Interim mitigation

Update the plugin to version 8.3.10 or later which includes proper nonce validation; until then, administrators should avoid clicking untrusted links while logged in.

Recommended fix High confidence

8.3.10

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the File Manager Pro plugin in the list
  4. If version 8.3.10 update is available, click 'Update Now' to install it
  5. Alternatively, download version 8.3.10 from the official WordPress repository or vendor site
  6. If automatic update is not available: deactivate the plugin, delete it, then upload and install version 8.3.10
  7. Verify the plugin shows version 8.3.10 after updating

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

Fix this in File Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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