File Manager Pro
CVE-2023-6846
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber account or obtain low-priv credentials
-
DeliveryAuthenticate to WordPress
-
ExploitSend crafted admin-ajax.php request to mk_check_filemanager_php_syntax
-
ExecutionUpload PHP webshell to server
-
PersistRequest webshell via HTTP
-
ImpactExecute arbitrary code as web server user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated WordPress account at the subscriber role or higher (PR:L), and the File Manager Pro plugin must be installed and active at version 8.3.4 or earlier. The practical limiting factor is account creation: on sites with open user registration enabled (a default for many WooCommerce, BuddyPress, LMS, and community deployments), attackers can self-provision the required account, effectively making this remotely exploitable; on sites with registration disabled, the attacker must first compromise or be issued any low-privilege credential. No user interaction is needed (UI:N), the attack is over the network (AV:N), and complexity is low (AC:L). |
| Impact | All signals point toward this being a genuine priority, not an inflated CVSS issue. The CVSS 8.8 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates network-reachable, low-complexity exploitation requiring only low privileges and no user interaction, with full CIA impact. EPSS of 13.31% (94th percentile) is unusually high and aligns with publicly available exploit code. The vulnerability is not currently listed in CISA KEV, so there is no confirmed active exploitation, but the combination of a public POC, trivial preconditions (a free subscriber account), and the prevalence of WordPress sites with open registration makes mass exploitation realistic. The only mitigating factor - PR:L instead of PR:N - is essentially meaningless on any site that permits self-registration, which is the default for WooCommerce, BuddyPress, LMS, and similar deployments. |
| Exploit ScenarioDerived | An attacker registers a free subscriber-level account on a vulnerable WordPress site (or uses any pre-existing low-privilege credential), then sends a crafted POST request to /wp-admin/admin-ajax.php invoking the mk_check_filemanager_php_syntax action with a malicious PHP payload. The plugin processes the request without verifying administrative capability and writes the payload to disk, which the attacker then requests over HTTP to achieve code execution as the web server user. A public POC is available, lowering the skill barrier considerably. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAI
Remote code execution in the WordPress File Manager Pro plugin (versions up to and including 8.3.4) allows authenticated attackers with subscriber-level access to upload arbitrary files via the mk_check_filemanager_php_syntax AJAX endpoint, leading to full server compromise. Publicly available exploit code exists, and the high EPSS score of 13.31% (94th percentile) indicates significant real-world exploitation likelihood. The flaw is patched in version 8.3.5, which introduces a missing capability check.
RemediationAI
Upgrade File Manager Pro to version 8.3.5 or later, which adds the capability check that prevents non-admin users from invoking mk_check_filemanager_php_syntax. Until the upgrade is applied, administrators should disable open user registration in WordPress (Settings → General → 'Anyone can register') to remove the subscriber attack surface - accepting the trade-off that this also blocks legitimate self-signup on membership/e-commerce sites; alternatively, disable or uninstall the File Manager Pro plugin entirely, which removes the file-management UI for admins but eliminates the vulnerable endpoint. A WAF rule blocking POST requests to admin-ajax.php with action=mk_check_filemanager_php_syntax from non-administrative sessions is a viable compensating control with low operational impact. Audit existing uploads, user accounts, and PHP files in wp-content for indicators of prior compromise before patching.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
File Manager Pro is a commercial WordPress plugin for managing files on the server through the WP admin interface. The root cause is CWE-94 (Improper Control of Generation of Code / Code Injection): the mk_check_filemanager_php_syntax AJAX action lacked a capability check, so any logged-in user - including the lowest-privilege subscriber role - could invoke functionality intended only for administrators and write PHP files into the webroot. WordPress sites that allow open user registration (a common e-commerce, membership, or community configuration) effectively expose this admin-only function to anyone on the internet. The CPE cpe:2.3:a:filemanagerpro:file_manager:*:*:*:*:*:wordpress:*:* covers all File Manager Pro plugin installations on WordPress.
Know when File Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
The File Manager Pro plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 8.3.4 via the mk_check_filemanager_php_syntax AJAX function. This makes it possible for authenticated attackers, with subscriber access and above, to execute code on the server. Version 8.3.5 introduces a capability check that prevents users lower than admin from executing this function.
Executive ViewAI
WordPress File Manager Pro plugin (versions ≤8.3.4) contains a remote code execution vulnerability allowing subscriber-level users to take control of servers. Publicly available exploit code and a 94th-percentile exploitation likelihood score create immediate risk of full server compromise for any organization running affected versions.
Apply vendor patch: version 8.3.5
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
More in File Manager
View allThe File Manager (wp-file-manager) plugin before 6.9 for WordPress allows remote attackers to upload and execute arbitra
The File Manager and File Manager Pro plugins for WordPress are vulnerable to Directory Traversal in versions up to, and
OS command injection in a family of popular WordPress file-manager plugins - FileOrganizer (before 1.1.9), Advanced File
Missing authorization controls in the File Manager WordPress plugin before version 6.9.1 allow any authenticated user -
Cross-site scripting in the WordPress File Manager plugin (below 8.0.5), FileOrganizer (below 1.2.1) and File Manager Pr
Unauthenticated information disclosure in the File Manager WordPress plugin before 6.9.1 exposes a REST API route withou
Missing capability checks in the File Manager WordPress plugin before version 6.9.1 expose the entire WordPress installa
mndpsingh287 WP File Manager v6.4 and lower fails to restrict external access to the fm_backups directory with a .htacce
The File Manager WordPress plugin before 6.3 does not restrict the file managers root directory, allowing an administrat
Unauthenticated information disclosure in the File Manager WordPress plugin (versions 7.2.2 through before 8.0.5) lets r
The File Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including,
In the default configuration of the File Manager WordPress plugin before 7.1, a Reflected XSS can occur on the endpoint
NVD
CVE.org
EPSS
GitHub
Exploit-DB