CVE-2025-50985: diskover-web · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 5.6 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 27 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, organizations should prioritize upgrading diskover-web to a version where the reflected XSS flaws are patched once available. In the interim, implement web application firewall (WAF) rules to detect and block suspicious requests containing script payloads in the affected GET parameters (maxage, maxindex, index, path, q, doctype). Input validation and output encoding should be enforced at the application layer to sanitize user-supplied input before reflection in HTML responses. Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of XSS attacks. Educate users about the risks of clicking untrusted links and encourage the use of security-aware browsing practices. Regularly monitor web server logs for unusual query parameter patterns indicative of attempted exploitation. Finally, conduct security assessments and penetration testing focused on web interface input handling to identify and remediate similar vulnerabilities proactively.
Description
diskover-web v2.3.0 Community Edition is vulnerable to multiple reflected cross-site scripting (XSS) flaws in its web interface. Unsanitized GET parameters including maxage, maxindex, index, path, q (query), and doctype are directly echoed into the HTML response, allowing attackers to inject and execute arbitrary JavaScript when a victim visits a maliciously crafted URL.