# CVE-2026-92976: Stored Cross-Site Scripting (XSS) in T-Systems’ TAO 2.0

> Authenticated users can inject malicious scripts into profile fields, leading to code execution and session hijacking when viewed by others.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-f95c-wf66-hq9m

## What is CVE-2026-92976?

CVE-2026-92976 is a medium-severity cross-site scripting vulnerability in T-Systems TAO, published on 18 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored Cross-Site Scripting (XSS) vulnerability in the profile management functionality of T-Systems’ TAO 2.0 suite. An authenticated user could inject malicious HTML or JavaScript content into the fields containing their personal data. The content entered is stored and displayed without being properly sanitised when another user, including administrative staff, views the affected profile. Successful exploitation could allow JavaScript code to be executed in the victim’s browser, access to information available within the session, or the performance of actions using the victim’s permissions.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-92976?


## How do I fix CVE-2026-92976?

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

## Is CVE-2026-92976 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92976 and fix it if it is affected.

What it is: CVE-2026-92976 is a medium-severity cross-site scripting vulnerability in T-Systems TAO, published on 18 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92976 in the wild and no public exploit code.

Affected product: T-Systems TAO. 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-2026-92976/ (Markdown: https://insights.sbomify.com/CVE-2026-92976/index.md)
```

## Sources

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

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