File Manager ProWordPress extension · Filemanagerpro.io
CVE-2024-7559
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 · uneditedThe File Manager Pro plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation and capability checks in the mk_file_folder_manager AJAX action in all versions up to, and including, 8.3.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary 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 · high confidenceThe File Manager Pro WordPress plugin has an arbitrary file upload vulnerability in the mk_file_folder_manager AJAX action. The plugin fails to validate file types and does not properly enforce capability checks, allowing any authenticated user with Subscriber-level access or higher to upload arbitrary files to the server. This can lead to remote code execution.
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 Manager ProWordPress extension
<= 8.3.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm File Manager Pro plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'File Manager Pro' or 'wp-file-manager' in the list of active plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status, indicates potential exposure.
-
Check installed plugin versionIn the Plugins list, click on the File Manager Pro plugin to view details, or inspect the plugin header in wp-content/plugins/wp-file-manager/file-manager-pro.php to find the 'Version' field.Affected if Version number is 8.3.7 or lower.
-
Verify AJAX endpoint accessibilityCheck if the mk_file_folder_manager AJAX action is publicly accessible by reviewing your WordPress site's AJAX setup or testing with a low-privilege (Subscriber role) user account making a POST request to /wp-admin/admin-ajax.php with action=mk_file_folder_manager.Affected if The AJAX endpoint responds to authenticated requests from users with Subscriber-level access without rejecting the request.
-
Inspect plugin directory for unauthorized filesReview all files in the wp-content/plugins/wp-file-manager/ folder, particularly the 'files' or 'upload' subdirectories if they exist, for unexpected PHP files, scripts, or files with suspicious extensions (.php, .phtml, .exe, .sh).Affected if Any unfamiliar files exist, especially executable or script files that were not intentionally uploaded by administrators.
-
Check for unauthorized admin accountsIn WordPress admin, go to Users > All Users and review the list for any unfamiliar accounts with Administrator role that may have been created through the vulnerability.Affected if New or unknown Administrator-level accounts exist that were not created by site administrators.
A user is affected if the File Manager Pro plugin version is 8.3.7 or lower and the mk_file_folder_manager AJAX action is accessible to authenticated users with Subscriber-level access or higher, or if suspicious files appear in the plugin directory.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the File Manager Pro plugin to version 8.3.8 or later. If immediate update is not possible, disable the plugin and audit the wp-content/plugins/wp-file-manager folder for any suspicious uploaded files.
File Manager Pro 8.3.8 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find File Manager Pro in the plugin list
- Click 'Update now' if an update is available, or manually upload the latest version from wordpress.org
- Verify the plugin version after update to confirm it shows a version higher than 8.3.7
- Review the uploads directory (/wp-content/uploads/) for any suspicious files that may have been uploaded during potential exploitation
- Ensure user roles are properly configured - Subscriber-level users should not have access to file management functionality unless explicitly required
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in File Manager Pro
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7559 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7559 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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