dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-11911

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 deletion due to insufficient file path validation in the eeSFL_DeleteFile function in all versions up to, and including, 6.3.7. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The simplefilelist_edit_job AJAX action is registered via wp_ajax_nopriv_, making it accessible without authentication, and the is_admin() guard that would otherwise restrict access is bypassed because is_admin() always returns true for requests to the admin-ajax.php endpoint.

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) contains an arbitrary file deletion vulnerability in the eeSFL_DeleteFile function. The issue stems from insufficient path validation allowing directory traversal, combined with the simplefilelist_edit_job AJAX action being exposed via wp_ajax_nopriv_ (no authentication required). The is_admin() check is ineffective because admin-ajax.php requests always return true for that function, bypassing intended access controls.

MitigationUpgrade to version 6.3.8 or later which implements proper file path validation and restricts the affected AJAX action. If immediate patching is not possible, consider disabling the plugin or blocking the simplefilelist_edit_job AJAX endpoint at the web server level.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Simple File List. Check the version number displayed below the plugin name.
    Affected if The installed version is 6.3.7 or earlier (any version up to and including 6.3.7).
  2. Confirm the vulnerable AJAX endpoint exists
    Examine the plugin source code for the simplefilelist_edit_job action registration. Look for lines containing 'wp_ajax_nopriv_simplefilelist_edit_job' or 'add_action("wp_ajax_nopriv_simplefilelist_edit_job"'. This endpoint handles the eeSFL_DeleteFile function.
    Affected if The action is registered with wp_ajax_noppriv_ (allowing unauthenticated access).
  3. Verify admin-ajax.php is reachable without authentication
    Send a request to /wp-admin/admin-ajax.php?action=simplefilelist_edit_job without providing any authentication cookies or credentials. Observe if the server returns a valid response rather than a 401/403 error.
    Affected if The AJAX endpoint responds without requiring authentication (the is_admin() check returns true for admin-ajax.php requests regardless of user session).
  4. Inspect the eeSFL_DeleteFile function for path validation
    Review the plugin file containing eeSFL_DeleteFile. Look for the file deletion logic and check whether it validates that the file path starts within the designated upload directory, and whether it sanitizes path traversal sequences (../).
    Affected if The function lacks proper path validation or does not block directory traversal sequences, allowing files outside the intended directory to be targeted.

A user is affected if the Simple File List plugin version is 6.3.7 or earlier, the simplefilelist_edit_job AJAX action is exposed without authentication, and the eeSFL_DeleteFile function lacks adequate path validation to prevent directory traversal.

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

Upgrade to version 6.3.8 or later which implements proper file path validation and restricts the affected AJAX action. If immediate patching is not possible, consider disabling the plugin or blocking the simplefilelist_edit_job AJAX endpoint at the web server level.

Recommended fix Moderate confidence

6.3.8 or later

  1. Check the WordPress plugin repository or the Simple File List plugin settings for the current installed version
  2. If the installed version is 6.3.7 or lower, navigate to Plugins > All Plugins in WordPress admin
  3. Find Simple File List in the plugins list
  4. Click Update Now if an update is available, or manually download the latest version from wordpress.org/plugins/simple-file-list/
  5. After updating, verify the version number reflects the fix (6.3.8 or higher)

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11911 — 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-11911 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