CVE-2025-50986: diskover-web · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 5.6 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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
Organizations should immediately audit their use of diskover-web v2.3.0 Community Edition and restrict administrative access to trusted personnel and secure environments. Until an official patch is released, administrators should avoid entering untrusted data into configuration fields and consider isolating the management interface from general network access using network segmentation or VPNs. Implementing Content Security Policy (CSP) headers can help mitigate the impact of XSS by restricting script execution sources. Monitoring administrative activity logs for unusual changes or access patterns is recommended. Additionally, organizations should follow vendor communications closely for patches or updates addressing this vulnerability. If feasible, upgrading to a later, patched version or applying custom input sanitization at the web server or proxy level could reduce risk. Training administrators on the risks of stored XSS and safe handling of configuration inputs is also advised.
Description
diskover-web v2.3.0 Community Edition suffers from multiple stored cross-site scripting (XSS) vulnerabilities in its administrative settings interface. Various configuration fields such as ES_HOST, ES_INDEXREFRESH, ES_PORT, ES_SCROLLSIZE, ES_TRANSLOGSIZE, ES_TRANSLOGSYNCINT, EXCLUDES_FILES, FILE_TYPES[], INCLUDES_DIRS, INCLUDES_FILES, and TIMEZONE do not properly sanitize user-supplied input. Malicious payloads submitted via these parameters are persisted in the application and executed whenever an administrator views or edits the settings page.