# CVE-2022-29882: Cross-site scripting in SICAM T

> An unauthenticated attacker can store XSS payloads via file uploads, allowing arbitrary actions when users view error logs.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2022
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-m366-vqxx-9f69

## What is CVE-2022-29882?

CVE-2022-29882 is a high-severity cross-site scripting vulnerability in Siemens SICAM T, published on 10 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in SICAM T (All versions < V3.0). Affected devices do not handle uploaded files correctly. An unauthenticated attacker could take advantage of this situation to store an XSS attack, which could - when a legitimate user accesses the error logs - perform arbitrary actions in the name of the user.

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

## Which versions are affected by CVE-2022-29882?

It affects 36 products.


Products: Siemens 7kg8500-0aa00-0aa0 Firmware, Siemens 7kg8500-0aa00-2aa0 Firmware, Siemens 7kg8500-0aa10-0aa0 Firmware, Siemens 7kg8500-0aa10-2aa0 Firmware, Siemens 7kg8500-0aa30-0aa0 Firmware, Siemens 7kg8500-0aa30-2aa0 Firmware, Siemens 7kg8501-0aa01-0aa0 Firmware, Siemens 7kg8501-0aa01-2aa0 Firmware, Siemens 7kg8501-0aa02-0aa0 Firmware, Siemens 7kg8501-0aa02-2aa0 Firmware, Siemens 7kg8501-0aa11-0aa0 Firmware, Siemens 7kg8501-0aa11-2aa0 Firmware, Siemens 7kg8501-0aa12-0aa0 Firmware, Siemens 7kg8501-0aa12-2aa0 Firmware, Siemens 7kg8501-0aa31-0aa0 Firmware, Siemens 7kg8501-0aa31-2aa0 Firmware, Siemens 7kg8501-0aa32-0aa0 Firmware, Siemens 7kg8501-0aa32-2aa0 Firmware, Siemens 7kg8550-0aa00-0aa0 Firmware, Siemens 7kg8550-0aa00-2aa0 Firmware and 16 more.

## How do I fix CVE-2022-29882?

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

## Is CVE-2022-29882 being exploited?

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

## Other vulnerabilities in Siemens SICAM T

- [CVE-2022-41665](https://insights.sbomify.com/CVE-2022-41665/): A vulnerability has been identified in SICAM P850 (7KG8500-0AA00-0AA0) (All versions < V3.10), SICAM P850 (7KG8500-0AA00-2AA0) (All versions (critical 9.8)
- [CVE-2022-29873](https://insights.sbomify.com/CVE-2022-29873/): Other in SICAM T (critical 9.3)
- [CVE-2022-29874](https://insights.sbomify.com/CVE-2022-29874/): Information disclosure in SICAM T (high 8.8)
- [CVE-2022-29872](https://insights.sbomify.com/CVE-2022-29872/): Other in SICAM T (high 8.7)
- [CVE-2022-40226](https://insights.sbomify.com/CVE-2022-40226/): Auth bypass in SICAM P850 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29882 and fix it if it is affected.

What it is: CVE-2022-29882 is a high-severity cross-site scripting vulnerability in Siemens SICAM T, published on 10 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29882 in the wild and no public exploit code.

Affected product: Siemens SICAM T. 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-2022-29882/ (Markdown: https://insights.sbomify.com/CVE-2022-29882/index.md)
```

## Sources

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

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