# CVE-2025-12776: Stored Cross-Site Scripting

> Stored XSS in Commvault WebConsole Report Builder allows script execution for users with edit permissions; the component is end-of-life and unsupported.

- **Severity:** Low 1.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-gj9v-28x2-5cxr

## What is CVE-2025-12776?

CVE-2025-12776 is a low-severity cross-site scripting vulnerability in Commvault WebConsole, published on 7 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-12776?

It affects 1 product.


Products: Commvault Commvault.

## How do I fix CVE-2025-12776?

No fix has been published for CVE-2025-12776 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12776 being exploited?

There is no known exploitation of CVE-2025-12776 in the wild and no public exploit code.

## Other vulnerabilities in Commvault WebConsole

- [CVE-2025-34028](https://insights.sbomify.com/CVE-2025-34028/): Commvault Command Center Path Traversal (critical 9.3, exploited in the wild)
- [CVE-2025-3928](https://insights.sbomify.com/CVE-2025-3928/): Commvault Web Server Unspecified (high 8.7, exploited in the wild)
- [CVE-2017-18044](https://insights.sbomify.com/CVE-2017-18044/): Command injection in n/a (critical 9.8)
- [CVE-2026-77089](https://insights.sbomify.com/CVE-2026-77089/): Command Center API Authentication Bypass (critical 9.3)
- [CVE-2026-13737](https://insights.sbomify.com/CVE-2026-13737/): Command Restriction Bypass (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12776 and fix it if it is affected.

What it is: CVE-2025-12776 is a low-severity cross-site scripting vulnerability in Commvault WebConsole, published on 7 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12776 in the wild and no public exploit code.

Affected product: Commvault WebConsole. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12776/ (Markdown: https://insights.sbomify.com/CVE-2025-12776/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12776
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12776
- OSV: https://osv.dev/vulnerability/CVE-2025-12776

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12776/
Summaries are generated and may contain mistakes; the official description above is the record.