# CVE-2022-50801: JM-DATA ONU JF511-TV 1.0.67 Authenticated Stored Cross-Site Scripting (XSS) Vulnerability

> Authenticated attackers can inject malicious scripts into JM-DATA ONU devices, leading to code execution in other users' browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/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:** 30 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-2v4h-c2w7-48pw

## What is CVE-2022-50801?

CVE-2022-50801 is a medium-severity cross-site scripting vulnerability in JM-DATA ONU JF511-TV, published on 30 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

JM-DATA ONU JF511-TV version 1.0.67 is vulnerable to authenticated stored cross-site scripting (XSS) attacks, allowing attackers with authenticated access to inject malicious scripts that will be executed in other users' browsers when they view the affected content.

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

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


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

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

## Is CVE-2022-50801 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50801 is a medium-severity cross-site scripting vulnerability in JM-DATA ONU JF511-TV, published on 30 Dec 2025. Any signed-in user can exploit it over the 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-50801 exists.

Affected product: JM-DATA ONU JF511-TV. 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-50801/ (Markdown: https://insights.sbomify.com/CVE-2022-50801/index.md)
```

## Sources

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

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