# CVE-2019-6487: Command injection in n/a

> Authenticated attackers can execute arbitrary commands on TP-Link WDR series routers via the weather citycode field.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5m66-hppq-vhmq

## What is CVE-2019-6487?

CVE-2019-6487 is a high-severity command injection vulnerability in n/a, published on 18 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TP-Link WDR Series devices through firmware v3 (such as TL-WDR5620 V3.0) are affected by command injection (after login) leading to remote code execution, because shell metacharacters can be included in the weather get_weather_observe citycode field.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2019-6487?

It affects 5 products.


Products: Tp-Link Tl-Wdr3500 Firmware, Tp-Link Tl-Wdr3600 Firmware, Tp-Link Tl-Wdr4300 Firmware, Tp-Link Tl-Wdr4900 Firmware, Tp-Link Tl-Wdr5620 Firmware.

## How do I fix CVE-2019-6487?

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

## Is CVE-2019-6487 being exploited?

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

Public exploit code:

- CVE-2019-6487. A command injection vulnerability in TP-Link WDR5620 Series up to verion 3. (github_poc): https://github.com/afang5472/TP-Link-WDR-Router-Command-injection_POC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6487 and fix it if it is affected.

What it is: CVE-2019-6487 is a high-severity command injection vulnerability in n/a, published on 18 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6487 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-2019-6487/ (Markdown: https://insights.sbomify.com/CVE-2019-6487/index.md)
```

## Sources

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

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