MEDIUM 6.5

CVE-2026-12119: WordPress Simple File List Plugin Authorization Bypass

The Simple File List WordPress plugin contains a flaw that allows authenticated users with basic contributor privileges to perform unauthorized file operations on a server. An attacker can exploit this by creating a draft post, extracting a security token from its preview, and then using that token to delete files, move files, create folders, or download files—bypassing the plugin's intended access controls. This affects all versions up to 6.3.7.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/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 unauthorized file operations due to a missing authorization check on the 'frontmanage' shortcode attribute in all versions up to, and including, 6.3.7. This makes it possible for authenticated attackers, with contributor-level access and above, to perform arbitrary file operations including deletion, move, folder creation, and download. An attacker can create a draft post containing the 'eeSFL' shortcode, render it via the post preview endpoint to harvest the nonce needed to authorize the operations, and then submit file operation requests that bypass the intended authorization checks in includes/ee-list-ops-bar-process.php.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-12119 is an authorization bypass vulnerability in the Simple File List WordPress plugin stemming from insufficient permission validation on the 'eeSFL' shortcode and related file operation handlers in includes/ee-list-ops-bar-process.php. The vulnerability permits authenticated users at contributor level or above to harvest valid nonces via the post preview endpoint and submit crafted requests that circumvent authorization checks. The attack chain does not require administrator privileges, social engineering, or user interaction beyond normal WordPress functionality, making it accessible to any authenticated account with minimal permissions.

Business impact

Organizations relying on Simple File List for content management or document handling face data loss, unauthorized file manipulation, and potential service disruption. An attacker with a low-privilege account—such as a freelancer or temporary contractor—could delete critical files, reorganize content structures, or exfiltrate sensitive documents without administrative oversight. The reputational and compliance implications depend on what files are stored; exposure of customer data, intellectual property, or regulated information amplifies risk.

Affected systems

All versions of the Simple File List WordPress plugin through version 6.3.7 are affected. The vulnerability is post-authentication, requiring an attacker to hold at least contributor-level access to a WordPress installation where the plugin is active. Multisite WordPress deployments and single-site installations are equally vulnerable if the plugin is enabled.

Exploitability

Exploitability is straightforward given low barriers to entry. An attacker needs valid WordPress credentials at contributor level—often granted to content creators, authors, or temporary staff—and no special tools or knowledge. The nonce extraction via post preview is a standard WordPress feature, and file operation requests can be crafted with basic HTTP knowledge. No user interaction is required once credentials are obtained. The vulnerability is not known to be actively exploited in the wild, but the attack surface and ease of execution make it a plausible target for insider threats and compromised low-privilege accounts.

Remediation

Update the Simple File List plugin to a patched version released after June 20, 2026 that implements proper authorization checks. Verify the patch version against the official WordPress plugin repository or vendor advisory. Until patching is feasible, restrict contributor-level access to users who genuinely require it, disable the plugin if it is not actively used, and monitor file operations and access logs for anomalous activity.

Patch guidance

Check the Simple File List plugin repository on wordpress.org for versions released after the vulnerability publication date of June 20, 2026. Apply the latest patched version through the WordPress admin dashboard. After updating, verify that file operation functionality still works as intended in a test environment. For sites unable to patch immediately, disable the plugin and re-enable it only after a fix is applied.

Detection guidance

Monitor WordPress audit logs and file access logs for unusual file deletion, movement, or download activity originating from contributor-level accounts. Look for POST requests to includes/ee-list-ops-bar-process.php with parameters indicative of file operations (delete, move, mkdir, download). Check for multiple file operations within a short window or operations targeting sensitive directories. Set up alerts on WordPress nonce generation and use via the preview endpoint, especially if followed by file operation requests from the same user session.

Why prioritize this

Although the CVSS score of 6.5 reflects medium severity, the practical risk is elevated by the low authentication barrier and insider threat potential. Contributor-level accounts are commonly granted to non-technical staff and external partners, widening the attack surface. File operations can cause immediate, irreversible damage (deletion, data loss). Organizations with strict least-privilege policies or those where file content is business-critical should prioritize patching. If the plugin is not essential, disabling it is the fastest mitigation.

Risk score, explained

The CVSS 3.1 score of 6.5 (MEDIUM) reflects the requirement for prior authentication (PR:L) and the absence of confidentiality impact (C:N). However, the integrity impact (I:H) is substantial—authorized file deletion and manipulation directly compromise data integrity. The score does not fully capture insider threat dynamics or the reputational cost of accidental data loss, which may justify accelerated patching in sensitive environments.

Frequently asked questions

Can an unauthenticated attacker exploit this vulnerability?

No. The vulnerability requires valid WordPress authentication at contributor level or above. An attacker without credentials cannot trigger the file operations, although they could target accounts with weak passwords or attempt credential compromise separately.

Does this vulnerability allow an attacker to execute code on the server?

No. The vulnerability is limited to file operations—deletion, movement, creation, and download. It does not provide code execution or direct shell access. However, deleting or modifying files could indirectly affect application stability or security.

What should we do if we cannot patch immediately?

Restrict contributor-level access to only trusted users who require it for their role. Disable the Simple File List plugin if it is not actively used. Enable detailed logging of file access and WordPress admin actions. Monitor for suspicious file operations and implement file integrity monitoring on critical directories.

Are there workarounds other than disabling the plugin?

Not reliably. The vulnerability is embedded in the authorization logic itself; there is no configuration setting that eliminates the risk without vendor intervention. Restricting access is damage control, not a fix. Patching is the definitive solution.

This analysis is based on vulnerability data published as of June 2026. CVSS scores and severity ratings reflect vendor assessments and may not capture all organizational risk factors. Patch version numbers should be verified against official vendor advisories before deployment. SEC.co does not distribute exploit code or weaponized proof-of-concept materials. Always test patches in a non-production environment before rolling out to production systems. Security posture depends on configuration, access controls, and monitoring capabilities in addition to patching. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).