# CVE-2019-16920: D-Link Multiple Routers Command Injection

> Unauthenticated attackers can execute arbitrary commands via the PingTest interface, leading to full system compromise on affected D-Link routers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-5p5j-jvxx-68mp

## What is CVE-2019-16920?

CVE-2019-16920 is a critical command injection vulnerability in n/a, published on 27 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated remote code execution occurs in D-Link products such as DIR-655C, DIR-866L, DIR-652, and DHP-1565. The issue occurs when the attacker sends an arbitrary input to a "PingTest" device common gateway interface that could lead to common injection. An attacker who successfully triggers the command injection could achieve full system compromise. Later, it was independently found that these are also affected: DIR-855L, DAP-1533, DIR-862L, DIR-615, DIR-835, and DIR-825.

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

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

It affects 10 products.


Products: Dlink Dap-1533 Firmware, Dlink Dhp-1565 Firmware, Dlink Dir-615 Firmware, Dlink Dir-652 Firmware, Dlink Dir-655 Firmware, Dlink Dir-825 Firmware, Dlink Dir-835 Firmware, Dlink Dir-855l Firmware, Dlink Dir-862l Firmware, Dlink Dir-866l Firmware.

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

No fix has been published for CVE-2019-16920 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2019-16920 being exploited?

Yes. Attackers have exploited CVE-2019-16920 in the wild since at least 25 Mar 2022.

Public exploit code:

- Exploit and Mass Pwn3r for CVE-2019-16920 (github_poc): https://github.com/eniac888/CVE-2019-16920-MassPwn3r
- D-Link Routers - Remote Code Execution (nuclei): http/cves/2019/CVE-2019-16920.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16920 is a critical command injection vulnerability in n/a, published on 27 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-16920 in the wild since at least 25 Mar 2022.

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-16920/ (Markdown: https://insights.sbomify.com/CVE-2019-16920/index.md)
```

## Sources

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

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