CVE-2026-38935
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/view.php via the doctype 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 in diskover-community version 2.3.5 and earlier allows remote attackers to inject malicious JavaScript through the doctype parameter in public/view.php. The vulnerable parameter reflects user-supplied input without proper sanitization or output encoding.
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. Common paths include /var/www/diskover, /opt/diskover, or check your web server document root for a 'diskover' folder containing public/ and other subdirectories.Affected if The diskover-community application is present on the system
-
Identify the installed versionCheck the version file or composer.json in the diskover root directory. Common commands: 'cat version' or 'grep version composer.json' or look for a VERSION file.Affected if The installed version is 2.3.5 or any version lower than 2.3.5
-
Verify public/view.php existsCheck for the file public/view.php within the diskover installation directory. This is the vulnerable script referenced in the CVE.Affected if The file public/view.php exists in the diskover installation
-
Confirm public access is enabledCheck your web server configuration to determine if the public/ directory is accessible via HTTP/HTTPS. Review Apache/nginx virtual host configuration for the diskover site.Affected if The public/ directory is web-accessible and exposes view.php to unauthenticated users
-
Test the doctype parameter for XSSSend a crafted request to public/view.php with a malicious payload in the doctype parameter, such as: http://[host]/public/view.php?doctype=<script>alert(1)</script>. Use browser developer tools or a proxy to observe if the payload is reflected unencoded in the response.Affected if The doctype parameter reflects the injected JavaScript payload directly in the HTML output without encoding
If diskover-community version 2.3.5 or earlier is installed, the public/view.php file is web-accessible, and the doctype parameter reflects unsanitized input, the environment is affected by this XSS vulnerability.
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 context-aware output encoding for the doctype parameter and/or add input validation to reject special characters (< > " ' /). Consider using a modern web framework's built-in XSS protection or a vetted sanitization library.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38935 — 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-38935 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