Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2020-25079

D-Link DCS-2530L and DCS-2670L Command Injection Vulnerability

D-Link DCS-2530L and DCS-2670L Devices

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.

CVSS
8.8
HIGH
EPSS
54%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
2 Sep 2020
CWE-77

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 5 August 2025. US federal agencies were required to remediate it by 26 August 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 54%, which is higher than 99% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2020-25079 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2020-25079.

What does CVE-2020-25079 affect?

CVE-2020-25079 affects D-Link DCS-2530L and DCS-2670L Devices. 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.

How severe is CVE-2020-25079?

CVE-2020-25079 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 54%, higher than 99% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 26 August 2025.

How should organisations respond to CVE-2020-25079?

Apply the vendor patch for D-Link DCS-2530L and DCS-2670L Devices as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.