What is CVE-2014-100005?

CVE-2014-100005 is D-Link DIR-600 Router Cross-Site Request Forgery (CSRF) Vulnerability. The supplied enrichment data classifies it as SSRF mapped to CWE-352 CWE-352.

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?

A public PoC is not confirmed from current sources for CVE-2014-100005. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with cloud metadata access logs, egress proxy logs 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-2014-100005 using CVSS 8, EPSS 42%, 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?

No public threat actor linkage is confirmed from current sources. 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 KEVhighSSRF

CVE-2014-100005

CVE-2014-100005 — D-Link DIR-600 Router Cross-Site Request Forgery (CSRF) Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2014-100005 in CISA KEV with required action: This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Multiple cross-site request forgery (CSRF) vulnerabilities in D-Link DIR-600 router (rev. Bx) with firmware before 2.17b02 allow remote attackers to hijack the authentication of administrators for requests that (1) create an administrator account or (2) enable remote management via a crafted configuration module to hedwig.cgi, (3) activate new configuration settings via a SETCFG,SAVE,ACTIVATE action to pigwidgeon.cgi, or (4) send a ping via a ping action to diagnostic.php.

Published Jan 13, 2015Updated Jun 17, 2026Sources: NVD, CISA, FIRST EPSS

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 May 16, 2024

EPSS

42%

ahead of 99% of scored CVEs

Affects

D-Link

DIR-600 Router

CVSS base

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

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade DIR-600 Router to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions.

Federal deadline Jun 6, 2024 — passed 812 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	DIR-600 Router	—	Vulnerable

Attack characteristics

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

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Adjacent

Privileges Req

Low

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
8	CVSS 3.1	high	2.1	5.9	NVD, CNA
6.8	CVSS 2.0	medium	8.6	6.4	NVD

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

Weakness & attack patterns

CWE-352

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery

CISA KEV details

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

CISAThat month →

Listed

May 16, 2024

Federal deadline

Jun 6, 2024

passed 812 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.

Detection

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

cloud metadata access logsegress proxy logs

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 8.0 (AV:A)
Jun 17, 2026 · NVD
2024
Added to CISA KEV catalog
May 16, 2024 · CISA
2015
Initial · CVE published
Jan 13, 2015 · NVD

References

7 on the record

resources.infosecinstitute.com/csrf-unauthorized-remote-admin-access/
Exploit, Third Party Advisory
secunia.com/advisories/57304
Broken Link
securityadvisories.dlink.com/security/publication.aspx?name=SAP10018
Patch, Vendor Advisory
exchange.xforce.ibmcloud.com/vulnerabilities/91794
Third Party Advisory, VDB Entry
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-100005
US Government Resource
legacy.us.dlink.com/pages/product.aspx?id=4587b63118524aec911191cc81605283
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2014-100005
Vendor Advisory

Elsewhere on this site

D-Linkevery CVE for this vendor
May 2024what else CISA listed
SSRFsame class
CWE-352other pages naming this weakness

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.

No confirmed IOCs, IP addresses, domains, file hashes, or malware 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-2014-100005 is D-Link DIR-600 Router Cross-Site Request Forgery (CSRF) Vulnerability, a high vulnerability affecting DIR-600 Router 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: A public PoC is not confirmed from current sources for CVE-2014-100005. 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 8 describes technical severity, while EPSS 42% 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.