CVE-2026-11912: Simple File List WordPress Plugin Authorization Bypass – File Modification Vulnerability
The Simple File List WordPress plugin contains a critical flaw that allows unauthenticated attackers to delete or modify files on vulnerable servers. The vulnerability exists in all versions up to 6.3.7 and stems from a flawed authorization mechanism. Specifically, the code checks whether a request appears to come from an admin before evaluating the actual permission setting that controls file management features. This means attackers can bypass the intended security control even on installations where the administrator has explicitly disabled the file management feature.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Weaknesses (CWE)
- CWE-862
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-20 / 2026-06-22
NVD description (verbatim)
The Simple File List plugin for WordPress is vulnerable to arbitrary file modification due to insufficient authorization checks in all versions up to, and including, 6.3.7. This makes it possible for unauthenticated attackers to delete and modify files on the serve. This vulnerability is exploitable even when the administrator has not enabled the AllowFrontManage setting, because the is_admin() check unconditionally short-circuits the guard before that setting is evaluated.
7 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-11912 is an authorization bypass vulnerability in Simple File List affecting versions ≤6.3.7. The vulnerability arises from improper authorization logic where an is_admin() check unconditionally short-circuits subsequent permission validation, including evaluation of the AllowFrontManage setting. This allows unauthenticated remote attackers to craft requests that bypass the intended access control, enabling arbitrary file deletion and modification operations. The flaw is classified under CWE-862 (Missing Authorization), with a CVSS v3.1 base score of 7.5 (High severity). The attack vector is network-based, requires no user interaction, and does not demand prior authentication or special privileges.
Business impact
Unrestricted file modification on WordPress sites poses substantial operational and confidentiality risks. Attackers can delete critical application files, corrupt configuration files, or inject malicious code into active theme and plugin files. This can lead to site defacement, malware installation, data exfiltration, or complete service disruption. Organizations relying on Simple File List for remote file management face particularly acute risk if the plugin is exposed to untrusted networks. Recovery from such compromise often requires forensic investigation, manual file restoration, and potential credential rotation across dependent systems.
Affected systems
The Simple File List WordPress plugin in all versions up to and including 6.3.7 is affected. The vulnerability is not dependent on WordPress core versions and affects any installation running a vulnerable version of the plugin, regardless of site configuration or the administrator's preference settings. Sites that have the plugin active but believe they have disabled the file management feature are equally vulnerable due to the authorization bypass.
Exploitability
This vulnerability is highly exploitable. It requires no authentication, no user interaction, and no special privilege escalation. An attacker with network access to the WordPress site can trigger the flaw via direct HTTP requests to affected endpoints. The authorization check flaw is unconditional, making exploitation straightforward. The vulnerability has not been designated as in-the-wild (KEV status: false as of the vulnerability's recent publication), but the simplicity of the attack pattern and the severity of the impact suggest rapid weaponization is likely.
Remediation
Immediately update the Simple File List plugin to a patched version released after 6.3.7. Verify the availability of a security patch from the plugin vendor before updating. As an interim mitigation, restrict HTTP access to the WordPress admin area and plugin endpoints using a Web Application Firewall (WAF) or network-level rules. Additionally, review file permissions on the server to limit the scope of damage an attacker can cause, and consider temporarily deactivating the plugin if it is not actively required.
Patch guidance
Check the Simple File List plugin repository or vendor advisory for a version newer than 6.3.7 that addresses this authorization flaw. Update via the WordPress admin dashboard's plugin update interface once a patched version is released and verified. Test the update in a staging environment first to ensure compatibility with your current WordPress configuration, themes, and other active plugins. After patching, review file access logs and recent file modifications to detect potential exploitation during the vulnerability window.
Detection guidance
Monitor for unauthenticated requests to Simple File List plugin endpoints that include file deletion or modification operations. Check server and web server logs for suspicious requests targeting the plugin's AJAX handlers or file management functions. Look for POST requests to plugin-specific endpoints originating from non-admin users or unusual geographic locations. Implement log aggregation and SIEM rules to flag any file deletion or modification events triggered by unauthenticated sessions. File integrity monitoring tools can alert on unauthorized changes to WordPress core files, themes, and plugins.
Why prioritize this
This vulnerability merits immediate patching priority due to its high CVSS score (7.5), ease of exploitation, and severe impact. The authorization bypass is unconditional and does not require exploitation of secondary factors. The ability to modify arbitrary files on the server means a single successful attack can compromise the entire WordPress installation and potentially pivot to other systems. Early patch deployment significantly reduces the attack surface.
Risk score, explained
The CVSS v3.1 score of 7.5 reflects a network-exploitable flaw with no authentication or user interaction required and high integrity impact. The vulnerability affects the confidentiality and integrity of file data on the affected server. The score does not account for widespread deployment of the Simple File List plugin across many WordPress installations, which amplifies the overall ecosystem risk. Organizations should consider threat modeling specific to their environment, including network exposure and data sensitivity.
Frequently asked questions
Will updating the plugin delete my existing files or settings?
A security patch should not affect your existing files or settings. Apply the update in a staging environment first to verify compatibility. Always maintain a backup before applying updates to production.
Is there a workaround if I cannot immediately patch?
Interim mitigations include disabling the Simple File List plugin entirely if not actively required, restricting HTTP access to plugin endpoints via firewall rules, and implementing Web Application Firewall rules to block suspicious requests. These do not fix the vulnerability but reduce exposure.
How can I tell if my site was exploited?
Review web server access logs and WordPress audit logs for unusual file modification events, especially those originating from unauthenticated requests or unexpected source IP addresses. Check file integrity using WordPress security plugins or manual comparison against a known-good backup.
Does this vulnerability affect WordPress.com or managed WordPress hosting?
This depends on whether the Simple File List plugin is installed and enabled on your specific site. Managed hosting providers may have additional protections or update policies. Contact your hosting provider for their remediation timeline.
This analysis is based on publicly available vulnerability data as of June 2026. Patch availability, vendor timelines, and exploitation status may change. Verify all patch versions, CVE details, and vendor advisories against official sources before deployment. This document does not constitute legal, compliance, or professional security advice. Organizations should conduct their own risk assessment and coordinate patching with their change management and testing procedures. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2018-25391HIGHHaPe PKH 1.1 Authorization Bypass – Unauthorized Record Deletion Vulnerability
- CVE-2024-32949HIGHMissing Authorization in Prince Integrate Google Drive — HIGH Risk
- CVE-2025-26418HIGHAndroid CarDevicePolicyService Privilege Escalation (CVSS 7.8)
- CVE-2025-48617HIGHAndroid CarrierConfigLoader Privilege Escalation Vulnerability
- CVE-2025-48640HIGHAndroid Passkey Permission Bypass Privilege Escalation
- CVE-2025-53345HIGHThimPress Thim Core Missing Authorization Leads to Code Execution
- CVE-2025-69189HIGHEMV JobBank Missing Authorization Vulnerability
- CVE-2026-0071HIGHAndroid SettingsLib Privilege Escalation Vulnerability