CVE-2020-25079: An issue was discovered on D-Link DCS-2530L before 1.06.01 Hotfix and DCS-2670L through 2.02 devices.
Noroxi assessment
Priority: Now (action score 81/100)
- CISA has confirmed exploitation in the wild (Aug 5, 2025). Remediation deadline for US federal agencies: Aug 26, 2025.
- Probability of exploitation in the next 30 days: 54% (FIRST EPSS); higher than 99% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Patch today or shut off access. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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.
- Published
- Sep 2, 2020
- Updated
- Jun 16, 2026
- EPSS
- 54.0% · 99th percentile
- CWE
- CWE-77
Report tools
Action score
81
Patch today or shut off access.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 16 / 30 · 54.0%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Aug 5, 2025. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Aug 26, 2025.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dlink | dcs-4703e firmware | cpe:2.3:o:dlink:dcs-4703e_firmware |
| dlink | dcs-4703e | cpe:2.3:h:dlink:dcs-4703e |
| dlink | dcs-4705e firmware | cpe:2.3:o:dlink:dcs-4705e_firmware |
| dlink | dcs-4705e | cpe:2.3:h:dlink:dcs-4705e |
| dlink | dcs-4802e firmware | cpe:2.3:o:dlink:dcs-4802e_firmware |
| dlink | dcs-4802e | cpe:2.3:h:dlink:dcs-4802e |
| dlink | dcs-p703 firmware | cpe:2.3:o:dlink:dcs-p703_firmware |
| dlink | dcs-p703 | cpe:2.3:h:dlink:dcs-p703 |
| dlink | dcs-4603 firmware | cpe:2.3:o:dlink:dcs-4603_firmware |
| dlink | dcs-4603 | cpe:2.3:h:dlink:dcs-4603 |
| dlink | dcs-4622 firmware | cpe:2.3:o:dlink:dcs-4622_firmware |
| dlink | dcs-4622 | cpe:2.3:h:dlink:dcs-4622 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dlink dcs-2530l firmwareup to 1.05.05 inclusive
- dlink dcs-2670l firmwarebefore 2.03.00
- dlink dcs-4603 firmwarebefore 1.04.02
- dlink dcs-4622 firmwarebefore 2.01.10
- dlink dcs-4701e firmwarebefore 2.03.01
- dlink dcs-4703e firmwarebefore 1.03.04
- dlink dcs-4705e firmwarebefore 1.03.02
- dlink dcs-4802e firmwarebefore 2.01.01
- dlink dcs-p703 firmwareall versions
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- CISA KEV+1797 d
- TodayNov 14, 2026+2264 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.