# CVE-2020-25506: D-Link DNS-320 Device Command Injection

> Remote attackers can execute arbitrary code on D-Link DNS-320 NAS devices via command injection in system_mgr.cgi.

- **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 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2021
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-vfrw-4wr4-4c85

## What is CVE-2020-25506?

CVE-2020-25506 is a critical command injection vulnerability in Dlink Dns-320 Firmware, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DNS-320 FW v2.06B01 Revision Ax is affected by command injection in the system_mgr.cgi component, which can lead to remote arbitrary code execution.

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

## Which versions are affected by CVE-2020-25506?

It affects 1 product.


Products: Dlink Dns-320 Firmware.

## How do I fix CVE-2020-25506?

No fix has been published for CVE-2020-25506 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-25506 being exploited?

Yes. Attackers have exploited CVE-2020-25506 in the wild since at least 3 Nov 2021.

Public exploit code:

- D-Link DNS-320 - Unauthenticated Remote Code Execution (nuclei): http/cves/2020/CVE-2020-25506.yaml

## Other vulnerabilities in Dlink Dns-320 Firmware

- [CVE-2019-16057](https://insights.sbomify.com/CVE-2019-16057/): D-Link DNS-320 Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2024-10914](https://insights.sbomify.com/CVE-2024-10914/): D-Link DNS-320/DNS-320LW/DNS-325/DNS-340L account_mgr.cgi cgi_user_add os command injection (critical 9.2)
- [CVE-2024-10915](https://insights.sbomify.com/CVE-2024-10915/): D-Link DNS-320/DNS-320LW/DNS-325/DNS-340L account_mgr.cgi cgi_user_add os command injection (critical 9.2)
- [CVE-2024-10916](https://insights.sbomify.com/CVE-2024-10916/): D-Link DNS-320/DNS-320LW/DNS-325/DNS-340L HTTP GET Request info.xml information disclosure (medium 6.9)
- [CVE-2024-8461](https://insights.sbomify.com/CVE-2024-8461/): D-Link DNS-320 Web Management Interface discovery.cgi information disclosure (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25506 and fix it if it is affected.

What it is: CVE-2020-25506 is a critical command injection vulnerability in Dlink Dns-320 Firmware, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-25506 in the wild since at least 3 Nov 2021.

Affected product: Dlink Dns-320 Firmware. 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-2020-25506/ (Markdown: https://insights.sbomify.com/CVE-2020-25506/index.md)
```

## Sources

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

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