# CVE-2016-20017: D-Link DSL-2750B Devices Command Injection

> Remote unauthenticated attackers can execute arbitrary commands on D-Link DSL-2750B routers via the login.cgi cli parameter.

- **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 8 Jan 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-4gf4-mg8f-6224

## What is CVE-2016-20017?

CVE-2016-20017 is a critical command injection vulnerability in n/a, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DSL-2750B devices before 1.05 allow remote unauthenticated command injection via the login.cgi cli parameter, as exploited in the wild in 2016 through 2022.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2016-20017?

It affects 1 product.


Products: Dlink Dsl-2750b Firmware.

## How do I fix CVE-2016-20017?

No fix has been published for CVE-2016-20017 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Jan 2024.

## Is CVE-2016-20017 being exploited?

Yes. Attackers have exploited CVE-2016-20017 in the wild since at least 8 Jan 2024.

Public exploit code:

- D-Link DSL-2750B OS Command Injection (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20017 and fix it if it is affected.

What it is: CVE-2016-20017 is a critical command injection vulnerability in n/a, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2016-20017 in the wild since at least 8 Jan 2024.

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

## Sources

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

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