CVE-2025-29635
CVE-2025-29635 — D-Link DIR-823X Command Injection Vulnerability
A command injection vulnerability in D-Link DIR-823X 240126 and 240802 allows an authorized attacker to execute arbitrary commands on remote devices by sending a POST request to /goform/set_prohibiting via the corresponding function, triggering remote command execution.
Published Updated Sources: NVD, D-Link (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory
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 Apr 24, 2026
EPSS
90%
ahead of 99.8% of scored CVEs
CVSS base
7.2
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.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
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-823X 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 May 8, 2026 — passed 112 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-823X | — | 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
Network
Privileges Req
High
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.2 | CVSS 3.1 | high | 1.2 | 5.9 | CNA |
| 8.8 | CVSS 3.1 | high | — | — | GHSA |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Weakness & attack patterns
- CWE-77Command Injection
Inferred from the weakness class — not observed against this CVE.
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Apr 24, 2026
Federal deadline
May 8, 2026
passed 112 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
3
1 of the 3 sampled are weaponized
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 /goform/set_prohibiting.
- Prioritize edge telemetry for network-reachable DIR-823X.
- Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.
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.2 (AV:N)
Jun 17, 2026 · NVD
Added to CISA KEV catalog
Apr 24, 2026 · CISA
- 2025
Initial · CVE published
Mar 25, 2025 · NVD
Added · GHSA-m9wc-3h85-pp63 published (high)
Mar 25, 2025 · GitHub Security Advisory
References
6 on the record
- github.com/mono7s/Dir-823x/blob/main/set_prohibiting/set_prohibiting.md
Broken Link, Exploit, Third Party Advisory
- www.akamai.com/blog/security-research/2026/apr/cve-2025-29635-mirai-campaign-targets-d-link-devices
Exploit, Third Party Advisory
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-29635
US Government Resource
- nvd.nist.gov/vuln/detail/CVE-2025-29635
NVD, Vendor Advisory
- github.com/advisories/GHSA-m9wc-3h85-pp63
Exploit, Third Party Advisory
- supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10469
Vendor Advisory
Elsewhere on this site
- D-Linkevery CVE for this vendor
- April 2026what else CISA listed
- Remote Code Execsame class
- CWE-77other 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-2025-29635 is D-Link DIR-823X Command Injection Vulnerability, a high vulnerability affecting DIR-823X 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: 3 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.2 describes technical severity, while EPSS 90% 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.