# CVE-2022-39996: Cross-site scripting in n/a

> An attacker can execute arbitrary code via a Cross-Site Scripting vulnerability in the upgrade/query.php page of Teldats routers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-6q99-8h4h-jqfw

## What is CVE-2022-39996?

CVE-2022-39996 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Aug 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cross Site Scripting vulnerability in Teldats Router RS123, RS123w allows attacker to execute arbitrary code via the cmdcookie parameter to the upgrade/query.php page.

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

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

It affects 2 products.


Products: Teldat Rs123 Firmware, Teldat Rs123w Firmware.

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

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

## Is CVE-2022-39996 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39996 exists.

Public exploit code:

- POC for CVE-2022-39996 (Reflected XSS) and CVE-2022-39997 (Weak Password) in Teldat RS123/RS123w Router (github_poc): https://github.com/uyhacked/Teldat-Router-CVE-2022-POC

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39996 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Aug 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39996 exists.

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-2022-39996/ (Markdown: https://insights.sbomify.com/CVE-2022-39996/index.md)
```

## Sources

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

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