# CVE-2014-4727: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via DHCP hostname, potentially compromising router admin sessions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v888-69w3-vqpv

## What is CVE-2014-4727?

CVE-2014-4727 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in the DHCP clients page in the TP-LINK N750 Wireless Dual Band Gigabit Router (TL-WDR4300) with firmware before 140916 allows remote attackers to inject arbitrary web script or HTML via the hostname in a DHCP request.

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

## Which versions are affected by CVE-2014-4727?

It affects 2 products.


Products: Tp-Link Tl-Wdr4300, Tp-Link Tl-Wdr4300 Firmware.

## How do I fix CVE-2014-4727?

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

## Is CVE-2014-4727 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4728](https://insights.sbomify.com/CVE-2014-4728/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4727 and fix it if it is affected.

What it is: CVE-2014-4727 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-4727 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-2014-4727/ (Markdown: https://insights.sbomify.com/CVE-2014-4727/index.md)
```

## Sources

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

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