# CVE-2025-11884: Cross-site Scripting vulnerability discovered in OpenText™ Universal Discovery and CMDB

> An attacker with high-level access can inject malicious scripts into uCMDB data, leading to stored cross-site scripting attacks.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L/S:N/AU:Y/R:U/V:C/RE:L/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-wr3x-gv3f-3792

## What is CVE-2025-11884?

CVE-2025-11884 is a low-severity cross-site scripting vulnerability in OpenText™ uCMDB, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in opentext uCMDB allows Stored XSS. The vulnerability could allow an attacker has high level access to UCMDB to create or update data with malicious scripts

This issue affects uCMDB: 24.4.

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

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


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

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

## Is CVE-2025-11884 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11884 is a low-severity cross-site scripting vulnerability in OpenText™ uCMDB, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11884 in the wild and no public exploit code.

Affected product: OpenText™ uCMDB. 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-11884/ (Markdown: https://insights.sbomify.com/CVE-2025-11884/index.md)
```

## Sources

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

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