# CVE-2016-10699: Cross-site scripting in n/a

> Remote attackers can inject persistent scripts into login fields, allowing them to hijack administrator sessions when logs are viewed.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g6q4-7xr2-9p55

## What is CVE-2016-10699?

CVE-2016-10699 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

D-Link DSL-2740E 1.00_BG_20150720 devices are prone to persistent XSS attacks in the username and password fields: a remote unauthenticated user may craft logins and passwords with script tags in them. Because there is no sanitization in the input fields, an unaware logged-in administrator may be a victim when checking the router logs.

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

## Which versions are affected by CVE-2016-10699?

It affects 1 product.


Products: Dlink Dsl-2740e Firmware.

## How do I fix CVE-2016-10699?

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

## Is CVE-2016-10699 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10699 and fix it if it is affected.

What it is: CVE-2016-10699 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-10699 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-2016-10699/ (Markdown: https://insights.sbomify.com/CVE-2016-10699/index.md)
```

## Sources

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

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