dbcve.org
File ManagerWordPress extension · Filemanagerpro

CVE-2024-8746

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 arbitrary backup file downloads and uploads due to missing file type validation via the 'mk_file_folder_manager_shortcode' ajax action in all versions up to, and including, 8.3.9. This makes it possible for unauthenticated attackers, if granted access to the File Manager by an administrator, to download and upload arbitrary backup files on the affected site's server which may make remote code execution possible.

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

The File Manager Pro WordPress plugin lacks file type validation in the 'mk_file_folder_manager_shortcode' ajax action, allowing unauthenticated attackers (who require admin-granted File Manager access) to download and upload arbitrary backup files. This arbitrary file access can lead to remote code execution.

MitigationUpdate File Manager Pro to the latest version after verifying a patch exists, and audit admin-configured access permissions to the File Manager functionality.

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. Verify File Manager Pro plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and search for 'File Manager Pro' or 'Filemanagerpro File Manager'
    Affected if Plugin is present indicates potential exposure to this vulnerability
  2. Check installed version against vulnerable range
    On the Plugins page, click the plugin name or 'View details' to display the version number. Compare this to the affected version threshold of 8.3.10
    Affected if Version is below 8.3.10 means the plugin is vulnerable
  3. Determine if File Manager access is open
    Review the plugin settings and access controls to see which user roles (administrator, editor, author, etc.) or if unauthenticated users can access the file manager functionality
    Affected if File Manager is accessible to unauthenticated users or low-privilege roles increases exploitability
  4. Look for unexpected backup archives
    Use the file manager or FTP to inspect wp-content/uploads/ and other directories for unknown .zip, .tar.gz, .bak, or backup files, particularly those with random names or recent creation dates
    Affected if Suspicious backup files exist that were not intentionally created may indicate exploitation

If File Manager Pro version below 8.3.10 is installed and the file manager is accessible (especially to non-admin users or unauthenticated attackers), the environment is affected by CVE-2024-8746.

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 File Manager Pro to the latest version after verifying a patch exists, and audit admin-configured access permissions to the File Manager functionality.

Recommended fix High confidence

8.3.10

  1. Navigate to the WordPress admin dashboard and update the File Manager Pro plugin to version 8.3.10 or later via Plugins > All Plugins > File Manager Pro > Update Now, or run 'wp plugin update file-manager-pro' using WP-CLI if available
  2. Verify the update was successful by confirming the installed version is 8.3.10 or higher in the Plugins section

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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