# CVE-2012-6316: Cross-site scripting in n/a

> Remote administrators can inject arbitrary scripts via username or password parameters in TP-LINK TL-WR841N routers, potentially leading to code execution or account takeover.

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

## What is CVE-2012-6316?

CVE-2012-6316 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Sep 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in the TP-LINK TL-WR841N router with firmware 3.13.9 Build 120201 Rel.54965n and earlier allow remote administrators to inject arbitrary web script or HTML via the (1) username or (2) pwd parameter to userRpm/NoipDdnsRpm.htm.

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

## Which versions are affected by CVE-2012-6316?

It affects 2 products.


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

## How do I fix CVE-2012-6316?

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

## Is CVE-2012-6316 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5687](https://insights.sbomify.com/CVE-2012-5687/): Path traversal in n/a (high 7.8)
- [CVE-2012-6276](https://insights.sbomify.com/CVE-2012-6276/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6316 and fix it if it is affected.

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

## Sources

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

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