# CVE-2020-25079: D-Link DCS-2530L and DCS-2670L Command Injection

> Authenticated attackers can execute arbitrary commands on D-Link IP cameras via the ddns_enc.cgi script.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 5 Aug 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-w49v-8458-hh85

## What is CVE-2020-25079?

CVE-2020-25079 is a high-severity command injection vulnerability in n/a, published on 2 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on D-Link DCS-2530L before 1.06.01 Hotfix and DCS-2670L through 2.02 devices. cgi-bin/ddns_enc.cgi allows authenticated command injection.

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

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

It affects 9 products.


Products: Dlink Dcs-2530l Firmware, Dlink Dcs-2670l Firmware, Dlink Dcs-4603 Firmware, Dlink Dcs-4622 Firmware, Dlink Dcs-4701e Firmware, Dlink Dcs-4703e Firmware, Dlink Dcs-4705e Firmware, Dlink Dcs-4802e Firmware, Dlink Dcs-P703 Firmware.

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

No fix has been published for CVE-2020-25079 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Aug 2025.

## Is CVE-2020-25079 being exploited?

Yes. Attackers have exploited CVE-2020-25079 in the wild since at least 5 Aug 2025.

## Other vulnerabilities in n/a

- [CVE-2020-25078](https://insights.sbomify.com/CVE-2020-25078/): D-Link DCS-2530L and DCS-2670L Devices Unspecified (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25079 is a high-severity command injection vulnerability in n/a, published on 2 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-25079 in the wild since at least 5 Aug 2025.

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

## Sources

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

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