# CVE-2021-29661: Cross-site scripting in n/a

> An attacker can inject JavaScript into trace files via the ITEMLISTVALUES parameter, which executes when authenticated users view the page.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 2 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v8wh-43jc-pfwj

## What is CVE-2021-29661?

CVE-2021-29661 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Apr 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Softing AG OPC Toolbox through 4.10.1.13035 allows /en/diag_values.html Stored XSS via the ITEMLISTVALUES##ITEMID parameter, resulting in JavaScript payload injection into the trace file. This payload will then be triggered every time an authenticated user browses the page containing it.

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

## Which versions are affected by CVE-2021-29661?

It affects 1 product.


Products: Softing Opc Toolbox.

## How do I fix CVE-2021-29661?

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

## Is CVE-2021-29661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-29660](https://insights.sbomify.com/CVE-2021-29660/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29661 and fix it if it is affected.

What it is: CVE-2021-29661 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Apr 2021. 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-2021-29661 in the wild and no public exploit code.

Affected product: n/a. 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-2021-29661/ (Markdown: https://insights.sbomify.com/CVE-2021-29661/index.md)
```

## Sources

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

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