Simple File List <= 6.3.7 - Missing Authorization to Unauthenticated File Modification via simplefilelist_edit_job AJAX Action
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
1- Range: <=6.3.7
Patches
Vulnerability mechanics
Root cause
"Unconditional short-circuit of authorization check via is_admin() before evaluating the AllowFrontManage setting, allowing unauthenticated file operations."
Attack vector
An unauthenticated attacker sends a crafted HTTP request to a WordPress endpoint served by the Simple File List plugin. The plugin's authorization logic checks `is_admin()` unconditionally; because `is_admin()` returns true for any WordPress-admin-based request, the guard exits early and never inspects the `AllowFrontManage` flag, which was intended to block front-end file operations. This permits arbitrary file deletion, modification, and creation on the server. [ref_id=1] documents the full set of filesystem operations (copy, move, delete, put_contents, etc.) that become reachable without authentication.
Affected code
The vulnerability resides in the authorization guard of the Simple File List plugin's `ee-functions.php` file. The plugin uses an unconditional `is_admin()` check that short-circuits the permission logic before the `AllowFrontManage` setting is evaluated, allowing unauthenticated attackers to reach file-manipulation functions such as `eeSFL_FileSystem`. [ref_id=1] shows the filesystem operations (copy, move, delete, put_contents, etc.) that become accessible as a result.
What the fix does
The advisory does not include a published patch, only a description of the flawed logic. The recommended fix is to restructure the authorization check so that `is_admin()` is not evaluated before the `AllowFrontManage` setting is examined; instead, the setting should be checked first, and `is_admin()` should only be used as a secondary gate. Without the patch, the unconditional `is_admin()` call allows every request to bypass the intended front-end restrictions.
Preconditions
- configAdministrator has not enabled the AllowFrontManage setting (default state).
Generated on Jun 20, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- plugins.trac.wordpress.org/browser/simple-file-list/tags/6.3.6/includes/ee-functions.phpmitre
- plugins.trac.wordpress.org/browser/simple-file-list/tags/6.3.6/includes/ee-functions.phpmitre
- plugins.trac.wordpress.org/browser/simple-file-list/tags/6.3.6/includes/ee-functions.phpmitre
- plugins.trac.wordpress.org/browser/simple-file-list/tags/6.3.6/includes/ee-list-display.phpmitre
- plugins.trac.wordpress.org/browser/simple-file-list/tags/6.3.6/simple-file-list.phpmitre
- plugins.trac.wordpress.org/changesetmitre
- www.wordfence.com/threat-intel/vulnerabilities/id/509a40d2-a33a-49ba-b858-fa8805127a1bmitre
News mentions
0No linked articles in our index yet.