Threats / D-Link / CVE-2020-25078
CVE-2020-25078
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
D-Link DCS-2530L and DCS-2670L Devices vulnerability
D-Link DCS-2530L and DCS-2670L devices contain an unspecified vulnerability enabling remote disclosure of administrator passwords, affecting end-of-life products.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can obtain administrator credentials from vulnerable D-Link network cameras, leading to full device compromise. Affected products are end-of-life with no vendor support.
CISA KEV Yes · 2025-08-054EPSS 0.97711 (verify live)5Exploit Public PoC6CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: partial3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-08-05).
Probability (EPSS)
EPSS 0.97711 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) · Affected: D-Link, DCS-2530L and DCS-2670L Devices. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1798 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I exploit the unspecified vulnerability to remotely extract the administrator password without authentication.
Business
Attackers gain administrative access to network cameras, enabling surveillance manipulation, lateral network movement, or device repurposing in botnets.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use obtained credentials to reconfigure camera settings, disable logging, or redirect video streams.
Business
Organizations lose visibility into physical security monitoring and cannot detect unauthorized access or tampering.
3
Lateral reach — past segmentation narrative 3
Attacker
I pivot from compromised cameras to other network segments using the device as an entry point.
Business
Internal network perimeter is breached, enabling broader infrastructure compromise and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05