dbcve.org
File ManagerWordPress extension · Filemanagerpro

CVE-2024-8918

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to 8.3.10 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Limited JavaScript File Upload in all versions up to, and including, 8.3.9. This is due to a lack of proper checks on allowed file types. This makes it possible for unauthenticated attackers, with permissions granted by an administrator, to upload .css and .js files, which could lead to Stored Cross-Site Scripting.

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 plugin for WordPress fails to properly validate file types during upload, allowing unauthenticated attackers (with administrator-granted permissions) to upload .css and .js files. This enables Stored Cross-Site Scripting (XSS) as the malicious scripts can be executed when users access the uploaded files.

MitigationUpdate the plugin to the latest version (after 8.3.9) which should include proper file type validation. Until then, review and restrict any administrator-granted permissions for unauthenticated users and audit existing uploaded files for malicious .js/.css files.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 the File Manager Pro plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Filemanagerpro File Manager' or 'File Manager Pro'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'file-manager' or similar naming.
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the File Manager Pro plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for a version constant or the plugin header comment.
    Affected if The version is lower than 8.3.10 (e.g., 8.3.9, 8.3.8, etc.)
  3. Identify if the plugin permits file uploads
    Access the plugin settings or file manager interface as an administrator. Navigate to the upload functionality and attempt to identify what file types are allowed or check the upload configuration settings.
    Affected if The plugin allows uploading files and .js/.css file extensions are not explicitly blocked in upload settings
  4. Audit uploaded files for malicious scripts
    Browse to the plugin's upload directory (typically /wp-content/plugins/file-manager/files/ or similar) using FTP or the WordPress file manager. List all .js and .css files. Inspect their contents for suspicious JavaScript (e.g., script tags, eval(), document.cookie, window.location) or CSS-based injection patterns.
    Affected if Any .js or .css files exist in the plugin's upload directory that contain malicious script tags or suspicious JavaScript code
  5. Review administrator-granted permissions for unauthenticated access
    In WordPress admin, go to Users > All Users or the plugin's user role/permission settings. Check if any users have been granted upload permissions and whether any shared credentials or backdoor accounts exist that could allow unauthenticated access to the file manager functionality.
    Affected if Unauthenticated or unexpected users have been granted file upload permissions through the plugin

If the File Manager Pro plugin version is below 8.3.10 and the plugin permits file uploads, the environment is likely affected by this stored XSS vulnerability.

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 the latest version (after 8.3.9) which should include proper file type validation. Until then, review and restrict any administrator-granted permissions for unauthenticated users and audit existing uploaded files for malicious .js/.css files.

Recommended fix High confidence

File Manager Pro plugin version 8.3.10 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins
  3. 3. Locate the File Manager Pro plugin
  4. 4. Click 'Update Now' to update to version 8.3.10 or later
  5. 5. Verify the plugin version shows 8.3.10 or higher after updating
  6. 6. Test file upload functionality to confirm the fix works correctly

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-8918 — 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-8918 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