What is CVE-2020-25078?

CVE-2020-25078 is D-Link DCS-2530L and DCS-2670L Devices Unspecified Vulnerability. The supplied enrichment data classifies it as Unclassified mapped to Not reported.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

41 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2020-25078 using CVSS 7.5, EPSS 98%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Void Rabisu (), RomCom (), APT 28 (), APT 5 (), APT 22 (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighpublic exploit

CVE-2020-25078

CVE-2020-25078 — D-Link DCS-2530L and DCS-2670L Devices Unspecified Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2020-25078 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

An issue was discovered on D-Link DCS-2530L before 1.06.01 Hotfix and DCS-2670L through 2.02 devices. The unauthenticated /config/getuser endpoint allows for remote administrator password disclosure.

Published Sep 2, 2020Updated Jun 17, 2026Sources: NVD, D-Link (CNA), CISA, FIRST EPSS, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 5, 2025

EPSS

98%

top of FIRST's scoreset

Affects

D-Link

DCS-2530L and DCS-2670L Devices

CVSS base

7.5

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade DCS-2530L and DCS-2670L Devices to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Aug 26, 2025 — passed 391 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
D-Link	DCS-2530L and DCS-2670L Devices	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.5	CVSS 3.1	high	3.9	3.6	NVD, CNA
5	CVSS 2.0	medium	10	2.9	NVD

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

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 5, 2025

Federal deadline

Aug 26, 2025

passed 391 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /config/getuser.
Prioritize edge telemetry for network-reachable DCS-2530L and DCS-2670L Devices.
Monitor for scanner or exploit-pattern traffic after 41 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Void RabisuRomComAPT 28APT 5APT 22

1 more threat groups on this CVEShowing 5 of 6 · Attribution, campaigns and the malware each one runsUnlock free

hash656ef3b170cbfe44759b470a9db51db8e035873269dabb0184ed97bb3b08443683
Public Malware Feeds · Nov 30, 2025
ip213.165.63.4949
SOCRadar Threat Exchange Services · Jul 21, 2026
ip89.208.97.16559
Blocklist.de-Firehol-APACHE · May 3, 2026
hash24576:4yqixz2+l4ukikpuwjax+xyidiz5ecnhebjzyir:4ex6+l+hznyuatnh0yir
SOCRadar Threat Exchange Services · Aug 27, 2026
hashb4735d8bef5759d8ce05ac916812d9c35b3eb704
SOCRadar Threat Exchange Services · Aug 27, 2026

1 more indicators on this CVEShowing 5 of 6 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.5 (AV:N)
Jun 17, 2026 · NVD
2025
Bulletin released on NIST.
Aug 7, 2025 · SOCRadar CTI
Cve is exploited D-Link DCS-2530L and DCS-2670L Devices Unspecified Vulnerability
Aug 6, 2025 · SOCRadar CTI
Added to CISA KEV catalog
Aug 5, 2025 · CISA
2023
CVE is exploited. "nomi-sec/PoC-in-GitHub"
Dec 15, 2023 · SOCRadar CTI
CVE is exploited. "yamori/pm2_logs"
Dec 15, 2023 · SOCRadar CTI
2020
Initial · CVE published
Sep 2, 2020 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

12×SVRS was changedAug 6, 2025 – Mar 29, 2026 · SOCRadar CTI
10×TweetsJan 18, 2025 – Mar 24, 2026 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelAug 6, 2025 · SOCRadar CTI
1×CVE modified by NIST: CISA KEV details updated.Aug 6, 2025 · SOCRadar CTI
1×Github_Repos · Github repository created, d4n-sec/d4n-sec.github.ioFeb 2, 2024 · SOCRadar CTI

References

5 on the record

supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10180
Patch, Vendor Advisory, NIST, MITRE_REFERENCES
twitter.com/Dogonsecurity/status/1273251236167516161
Broken Link, Third Party Advisory, NIST, MITRE_REFERENCES
support.dlink.com/productinfo.aspx?m=DCS-2530L
Product, NIST, Vendor Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-25078
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2020-25078
Vendor Advisory

Coverage

3 stories from the feeds we poll

Elsewhere on this site

D-Linkevery CVE for this vendor
August 2025what else CISA listed
Unclassifiedsame class

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2020-25078 is D-Link DCS-2530L and DCS-2670L Devices Unspecified Vulnerability, a high vulnerability affecting DCS-2530L and DCS-2670L Devices from D-Link. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 41 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 98% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.