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

> An attacker can inject arbitrary HTML/JavaScript via crafted DHCP packets to achieve client-side code execution on the router's lease-status table.

- **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:** 9 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vgr2-xrrq-jr2p

## What is CVE-2019-14918?

CVE-2019-14918 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

XSS in the DHCP lease-status table in Billion Smart Energy Router SG600R2 Firmware v3.02.rc6 allows an attacker to inject arbitrary HTML/JavaScript code to achieve client-side code execution via crafted DHCP request packets to etc_ro/web/internet/dhcpcliinfo.asp.

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

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

It affects 1 product.


Products: Billion Sg600 R2 Firmware.

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

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

## Is CVE-2019-14918 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14920](https://insights.sbomify.com/CVE-2019-14920/): Command injection in n/a (high 8.8)
- [CVE-2019-14919](https://insights.sbomify.com/CVE-2019-14919/): Hardcoded credentials in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14918 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jan 2020. 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-2019-14918 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-14918/ (Markdown: https://insights.sbomify.com/CVE-2019-14918/index.md)
```

## Sources

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

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