dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-11912

HIGH · 7.5 CVSS v3.1 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The Simple File List WordPress plugin (versions up to 6.3.7) has a broken access control vulnerability where the is_admin() check short-circuits before the AllowFrontManage setting is evaluated, allowing unauthenticated attackers to arbitrarily delete or modify files on the server regardless of the admin configuration.

MitigationUpdate the plugin to version 6.3.8 or later which properly evaluates authorization before the is_admin() check. If immediate patching is not feasible, disable or remove the plugin until the update can be applied.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Simple File List plugin is installed
    Navigate to WordPress admin > Plugins and verify Simple File List appears in the list of installed plugins, or inspect the plugin files in /wp-content/plugins/simple-file-list/ for the main PHP file containing the version header
    Affected if The plugin is not installed
  2. Identify the installed plugin version
    Locate the plugin version number in the plugin header of the main file (ee-simple-file-list.php or similar) within the plugin directory, or view the version displayed on the Plugins page in WordPress admin
    Affected if Version is 6.3.7 or earlier
  3. Check if AllowFrontManage setting is enabled
    In WordPress admin, go to Simple File List settings and look for the 'Allow Front-End Manage' or 'AllowFrontManage' option; alternatively, inspect the plugin options in the wp_options table where the setting is stored
    Affected if AllowFrontManage is set to enabled or yes (this configuration combined with vulnerable version creates the exposure)
  4. Verify file operation endpoints are accessible
    Test access to the plugin AJAX endpoints or file management URLs (typically under /wp-admin/admin-ajax.php?action=eeFileList... or similar) using an unauthenticated browser or curl request to confirm they respond without login
    Affected if Unauthenticated requests to file delete/modify endpoints return success rather than redirecting to login

If Simple File List plugin is installed at version 6.3.7 or earlier AND AllowFrontManage is enabled, the environment is affected by this unauthenticated file manipulation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 6.3.8 or later which properly evaluates authorization before the is_admin() check. If immediate patching is not feasible, disable or remove the plugin until the update can be applied.

Recommended fix High confidence

6.3.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Simple File List plugin in the list
  4. Click 'Update now' if an update is available, or manually upload version 6.3.8 or later
  5. Verify the update completed successfully
  6. Confirm the new version number in the plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11912 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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