Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.1

How to Fix CVE-2026-38936: n/a (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-38936 is a sibling vulnerability in the same vendor advisory as CVE-2026-38934. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 6.1 - Medium
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-38934
Fixed inSame patched build as CVE-2026-38934 (See vendor advisory)
Type (CWE)n/a

What's different about CVE-2026-38936?

A reflected cross-site scripting (XSS) vulnerability exists in diskover-community <= 2.3.5 in public/selectindices.php via the namecontains parameter

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-38936

Apply the patched build per the primary write-up: How to Fix CVE-2026-38934.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-38936 fixed by the same patch as CVE-2026-38934?

Yes. CVE-2026-38936 ships in the same vendor advisory as CVE-2026-38934. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-38936?

The CVSS base score is 6.1 (Medium).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the n/a bundle. Full procedure at CVE-2026-38934.*