What is the CVSS score of CVE-2019-6487?

CVE-2019-6487 has a CVSS 3.0 base score of 8.8 (High). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 8.5%.

Is there a public PoC exploit available for CVE-2019-6487?

Yes, a public proof-of-concept exploit is available for CVE-2019-6487. Prioritise patching immediately. EPSS: 8.5%.

Tl Wdr5620 Firmware CVE-2019-6487

HIGH

OS Command Injection (CWE-78)

2019-01-18 cve@mitre.org

TP-Link RCE Command Injection Tl Wdr5620 Firmware Tl Wdr3500 Firmware Tl Wdr3600 Firmware Tl Wdr4300 Firmware Tl Wdr4900 Firmware

8.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jan 18, 2019 - 10:29 nvd

HIGH 8.8

DescriptionNVD

AnalysisAI

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. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. 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. Affected products include: Tp-Link Tl-Wdr5620 Firmware, Tp-Link Tl-Wdr3500 Firmware, Tp-Link Tl-Wdr3600 Firmware, Tp-Link Tl-Wdr4300 Firmware, Tp-Link Tl-Wdr4900 Firmware.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.