# CVE-2018-14497: Cross-site scripting in n/a

> Attackers can inject malicious scripts into the SSID field of Tenda D152 routers, potentially compromising user sessions or executing code.

- **Severity:** Medium 5.4 (`CVSS:3.0/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:** 3 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q86w-c9hx-83fq

## What is CVE-2018-14497?

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

### Official description

Tenda D152 ADSL routers allow XSS via a crafted SSID.

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

## Which versions are affected by CVE-2018-14497?

It affects 1 product.


Products: Tendacn D152 Firmware.

## How do I fix CVE-2018-14497?

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

## Is CVE-2018-14497 being exploited?

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

Public exploit code:

- Tenda ADSL Router D152 - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14497 and fix it if it is affected.

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

## Sources

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

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