CVE-2026-38936
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 · uneditedA reflected cross-site scripting (XSS) vulnerability exists in diskover-community <= 2.3.5 in public/selectindices.php via the namecontains parameter
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in diskover-community versions 2.3.5 and earlier. The vulnerability is located in public/selectindices.php via the namecontains parameter, which does not properly sanitize user-supplied input before reflecting it back in the HTTP response, allowing attackers to inject malicious JavaScript code.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm diskover-community is installedLocate the diskover installation directory on the system; common paths include /var/www/html/diskover, /opt/diskover, or the web server document root. Look for the main index.php or diskover-web.php files.Affected if The application files are present on the system.
-
Identify the installed versionCheck the version file in the diskover installation directory, typically named VERSION, version.php, or consult the composer.json file. Alternatively, access the web interface and check any About or System Info page.Affected if The installed version is 2.3.5 or earlier.
-
Verify the vulnerable script existsCheck if public/selectindices.php exists in the diskover installation directory. This file handles the selectindices functionality and contains the namecontains parameter handler.Affected if The file public/selectindices.php exists and is accessible via the web server.
-
Confirm web access is enabledVerify that the web server (Apache, Nginx, or built-in PHP server) is running and the diskover public directory is accessible via HTTP/HTTPS. The XSS flaw requires the web interface to be reachable.Affected if The application web interface is accessible and the selectindices.php endpoint responds to requests.
-
Test for parameter reflection without sanitizationSend a request to public/selectindices.php with a test payload in the namecontains parameter, such as namecontains=test. Examine the HTTP response to see if the input is reflected back without encoding or sanitization.Affected if The namecontains parameter value is reflected in the response without HTML encoding or sanitization applied.
The environment is affected if diskover-community version 2.3.5 or earlier is installed, the public/selectindices.php file exists, and the namecontains parameter reflects user input without sanitization.
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 dataImplement proper input validation and output encoding on the namecontains parameter in selectindices.php. Sanitize or escape special characters (<, >, ", ', script tags) before reflecting user input in the response.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38936 — 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-38936 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