# CVE-2019-12195: Cross-site scripting in n/a

> An attacker with admin access can inject XSS via the network name, causing a denial of service by disconnecting all users from the internet.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j3f3-xxfp-q982

## What is CVE-2019-12195?

CVE-2019-12195 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 May 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

TP-Link TL-WR840N v5 00000005 devices allow XSS via the network name. The attacker must log into the router by breaking the password and going to the admin login page by THC-HYDRA to get the network name. With an XSS payload, the network name changed automatically and the internet connection was disconnected. All the users become disconnected from the internet.

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

## Which versions are affected by CVE-2019-12195?

It affects 1 product.


Products: Tp-Link Tl-Wr840n Firmware.

## How do I fix CVE-2019-12195?

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

## Is CVE-2019-12195 being exploited?

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

Public exploit code:

- TP-LINK TL-WR840N v5 00000005 - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-25060](https://insights.sbomify.com/CVE-2022-25060/): Command injection in n/a (critical 9.8)
- [CVE-2022-25061](https://insights.sbomify.com/CVE-2022-25061/): Command injection in n/a (critical 9.8)
- [CVE-2022-25064](https://insights.sbomify.com/CVE-2022-25064/): Command injection in n/a (critical 9.8)
- [CVE-2021-41653](https://insights.sbomify.com/CVE-2021-41653/): Command injection in n/a (critical 9.8)
- [CVE-2020-36178](https://insights.sbomify.com/CVE-2020-36178/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12195 and fix it if it is affected.

What it is: CVE-2019-12195 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 May 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12195 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-2019-12195/ (Markdown: https://insights.sbomify.com/CVE-2019-12195/index.md)
```

## Sources

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

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