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

> Attackers can inject malicious scripts via the Add User feature on D-Link DIR-615 T1 routers, potentially compromising user sessions.

- **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:** 18 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6j4j-c9wg-pj7g

## What is CVE-2018-10110?

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

### Official description

D-Link DIR-615 T1 devices allow XSS via the Add User feature.

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

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

It affects 1 product.


Products: D-Link Dir-615 T1 Firmware.

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

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

## Is CVE-2018-10110 being exploited?

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

Public exploit code:

- D-Link DIR-615 Wireless Router - Persistent Cross Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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