CVE-2026-57382
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Mitchell Bennis Simple File List simple-file-list allows Reflected XSS.This issue affects Simple File List: from n/a through <= 6.3.8.
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 · moderate confidenceReflected XSS vulnerability in the Simple File List WordPress plugin allows remote attackers to inject malicious JavaScript through unsanitized user input that gets rendered in web pages without proper output encoding. The vulnerability exists in versions up to and including 6.3.8.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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, or check the filesystem at wp-content/plugins/simple-file-list/ for the plugin filesAffected if The plugin is present and active in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, view the plugin details page to see the version number, or open simple-file-list/readme.txt and look for the 'Stable tag' valueAffected if The version is 6.3.8 or any earlier version (the affected range includes all versions up to and including 6.3.8)
-
Confirm the plugin is accessible on the frontendVisit a page where the file list shortcode [eeSFL] or the file list is expected to display, or check if the shortcode is present in any published pages/postsAffected if The file list functionality is actively being used or exposed on the site
-
Identify if user-supplied input is rendered in the file listUpload a test file with a filename containing a benign script tag (for example: test<img src=x onerror=alert(1)>.txt) and then view the file list page to see if the filename is rendered without encodingAffected if The filename or any user input field is displayed back to the browser without HTML entity encoding (the raw script tag appears in the page source)
A user is affected if Simple File List version 6.3.8 or earlier is installed, the plugin is active, and user-supplied input such as filenames are rendered in web pages without proper output encoding.
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.
From vendor dataUpdate Simple File List to the latest patched version which implements proper input validation and output encoding, or apply a WAF rule to block XSS payloads in the interim while testing the update.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57382 — 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-57382 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