Threats / D-Link / CVE-2014-100005
CVE-2014-100005
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
D-Link DIR-600 Router vulnerability
D-Link DIR-600 routers are vulnerable to cross-site request forgery (CSRF) attacks that allow attackers to modify router configurations by exploiting authenticated administrator sessions.
Verdict
Today item — known-exploited.
An attacker can craft malicious web pages that, when visited by an authenticated router administrator, execute unauthorized configuration changes. This vulnerability has been observed in active exploitation and affects router security posture and network integrity.
CISA KEV Yes · 2024-05-164EPSS 0.43456 (verify live)5CVSS 8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 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 2024-05-16).
Probability (EPSS)
EPSS 0.43456 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8 (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: D-Link, DIR-600 Router. 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.
Weakness (CWE)
Mapped to CWE-352 Cross-Site Request Forgery (CSRF) — weakness family: Web / client.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA'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 3411 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 functional/weaponized public exploit). Catalog entries: Metasploit module. 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 craft a malicious webpage containing hidden requests that target the router's administrative interface.
Business
Attackers gain ability to reconfigure network devices without direct authentication, increasing breach surface.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trick an administrator into visiting my page while they maintain an active session with the router.
Business
Administrative session hijacking becomes viable, enabling unauthorized network modifications at scale.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify router settings such as DNS, port forwarding, or wireless credentials through forged requests.
Business
Network traffic can be redirected, devices isolated, or credentials compromised, undermining infrastructure security.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.