CVE-2026-12119
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 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.
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 Simple File List WordPress plugin (versions up to 6.3.7) contains a missing authorization vulnerability in the 'frontmanage' shortcode attribute. Authenticated attackers with contributor-level access can create a draft post with the 'eeSFL' shortcode, preview it to harvest a nonce, then submit requests to includes/ee-list-ops-bar-process.php that bypass authorization checks, enabling arbitrary file operations including deletion, move, folder creation, and download.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Verify Simple File List plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Simple File List' in the list. Note the version number displayed.Affected if The plugin is installed and the version is 6.3.7 or earlier, or if the version cannot be determined and the plugin is present.
-
Check for the vulnerable PHP fileLocate the file 'includes/ee-list-ops-bar-process.php' within the Simple File List plugin directory on the server. This file handles the file operations that can be exploited.Affected if The file exists in the plugin directory, indicating the vulnerable code is present.
-
Identify use of the frontmanage shortcodeSearch WordPress posts, pages, and custom post types for the shortcode 'eeSFL' with the 'frontmanage' attribute (e.g., [eeSFL frontmanage=yes] or [eeSFL frontmanage='1']). Use WordPress admin's Posts/Pages list or query the wp_posts database table for this shortcode.Affected if Any post or page contains the eeSFL shortcode with the frontmanage attribute enabled.
-
Review server access logs for suspicious requestsExamine web server access logs for POST requests to 'includes/ee-list-ops-bar-process.php' originating from authenticated users with contributor-level or lower permissions. Look for unusual parameters such as 'eeSFL_action' with values like 'delete', 'move', 'create_folder', or 'download'.Affected if Requests to the vulnerable endpoint are found from users who should not have file management privileges.
-
Check for unauthorized file modificationsReview the file list managed by Simple File List for any unexpected deletions, moves, or newly created folders. Compare current file listings against known-good backups or monitor for recent changes to the upload directory.Affected if File operations have occurred that were not initiated by administrators or that do not match expected user activity.
A user is affected if the Simple File List plugin version is 6.3.7 or earlier, the ee-list-ops-bar-process.php file exists, and either the frontmanage shortcode is in use or suspicious requests to the vulnerable endpoint appear in logs.
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 to Simple File List version 6.3.8 or later which includes proper authorization checks on the frontmanage functionality.
Simple File List plugin version 6.3.8 or later
- 1. Update the Simple File List WordPress plugin to the latest available version from the WordPress plugin repository.
- 2. After updating, verify that the 'frontmanage' shortcode attribute now properly checks for authorization before allowing file operations.
- 3. Ensure that contributors cannot perform administrative file operations without appropriate capabilities.
- 4. Review user roles and permissions to confirm the authorization controls are working as expected.
- 5. Consider implementing additional security measures such as limiting which user roles can preview draft posts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12119 — 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-2026-12119 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