CVE-2020-25079
RCE in Dlink Dcs-4703E Firmware ≤ 1.03.04
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2020-25079 is a high-severity Command Injection (CWE-77) vulnerability in Dlink Dcs-4703E Firmware. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2020-25079 is an authenticated command injection vulnerability (CWE-77) affecting the cgi-bin/ddns_enc.cgi endpoint on D-Link DCS-2530L devices prior to firmware 1.06.01 Hotfix and DCS-2670L devices through firmware version 2.02. The flaw carries a CVSS 3.1 base score of 8.8, reflecting network attack vector, low attack complexity, and low privileges required.
An attacker who has already obtained valid credentials can send specially crafted requests to the affected CGI script, resulting in arbitrary command execution on the device. Successful exploitation grants the attacker full control over confidentiality, integrity, and availability of the camera without user interaction.
Vendor advisories referenced in the disclosure direct users to the D-Link support portal for the DCS-2530L hotfix and updated firmware for the DCS-2670L; the same announcements list the affected models and corresponding fixed versions. No public information on in-the-wild exploitation is provided in the available references.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-17771
Vulnerability Data
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.
- CWE(s)
- KEV Date Added
- 05 August 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.