CVE-2025-12776: Commvault WebConsole · XSS or 'Cross-site Scripting'
Affects Commvault WebConsoleSource CVE Database V5
Not known to be exploited · CVSS 1.8 Low · end of life, no fix coming : replace or isolate Commvault WebConsole; no fix will be released.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- None coming – the product is end of life
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jan 2026
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
No fix will be released: Commvault WebConsole is end of life. Replace it, or isolate it from untrusted networks until you can.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CommvaultWebConsole | Affected
| Fixed in– |
AI-suggested
Given the WebConsole is end-of-life, the primary mitigation is to discontinue its use in production environments entirely. If continued use is unavoidable, deploy the WebConsole and Report Builder within a fully isolated network segment that has no connectivity to sensitive data repositories or the internet. Restrict edit permissions strictly to trusted administrators and monitor all report modifications for suspicious activity. Employ network segmentation and strict access controls to limit exposure. Consider migrating to supported Commvault products or alternative solutions that receive regular security updates. Additionally, implement web application firewalls (WAFs) to detect and block potential XSS payloads targeting the Report Builder interface. Regularly audit user permissions and logs to detect unauthorized access or attempts to exploit this vulnerability. Since no patches are available, compensating controls and isolation are essential.
Description
The Report Builder component of the application stores user input directly in a web page and displays it to other users, which raised concerns about a possible Cross-Site Scripting (XSS) attack. Proper management of this functionality helps ensure a secure and seamless user experience. Although the user input is not validated in the report creation, these scripts are not executed when the report is run by end users. The script is executed when the report is modified through the report builder by a user with edit permissions. The Report Builder is part of the WebConsole. The WebConsole package is currently end of life, and is no longer maintained. We strongly recommend against installing or using it in any production environment. However, if you choose to install it, for example, to access functionality like the Report Builder, it must be deployed within a fully isolated network that has no access to sensitive data or internet connectivity. This is a critical security precaution, as the retired package may contain unpatched vulnerabilities and is no longer supported with updates or fixes.