Threats / D-Link / CVE-2025-29635
CVE-2025-29635
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
D-Link DIR-823X vulnerability
D-Link DIR-823X contains a command injection vulnerability in the /goform/set_prohibiting endpoint that allows authorized attackers to execute arbitrary commands on affected devices.
Verdict
Today item — known-exploited.
An authenticated attacker can inject and execute arbitrary system commands on vulnerable DIR-823X routers through a POST request, potentially compromising device integrity and network security. The product is reportedly end-of-life or end-of-service.
CISA KEV Yes · 2026-04-244EPSS 0.89641 (verify live)5CVSS 7.2 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Public PoC / detection · nuclei template12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
11 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 2026-04-24).
Probability (EPSS)
EPSS 0.89641 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) · Affected: D-Link, DIR-823X. 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-77 Command Injection — weakness family: Injection.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 395 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 craft a malicious POST request to /goform/set_prohibiting with injected shell commands embedded in the request parameters.
Business
An insider or compromised account holder gains unauthorized command execution capability on network infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands with the privileges of the web service process to modify device configuration, install backdoors, or pivot to other network segments.
Business
Device compromise enables lateral movement, data exfiltration, or persistent unauthorized access to the network.
3
Lateral reach — past segmentation narrative 3
Attacker
I maintain persistence by modifying startup scripts or installing rootkits that survive device reboots.
Business
Long-term compromise of network perimeter security increases exposure to advanced threats and regulatory violations.
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