CVE-2025-9026
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was identified in D-Link DIR-860L 2.04.B04. This affects the function ssdpcgi_main of the file htdocs/cgibin of the component Simple Service Discovery Protocol. The manipulation leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in the Simple Service Discovery Protocol (SSDP) component of D-Link DIR-860L routers (firmware 2.04.B04). The ssdpcgi_main function in htdocs/cgibin fails to sanitize user input, allowing remote attackers to execute arbitrary operating system commands without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.04.b04CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLog into the router web interface or check the device label to confirm the model is D-Link DIR-860L.Affected if The device is a D-Link DIR-860L router.
-
Check the firmware versionAccess the router web interface (typically at 192.168.0.1), navigate to Status or System settings, and locate the firmware version information. Alternatively, check the label on the device itself.Affected if The firmware version is exactly 2.04.B04.
-
Verify SSDP service availabilityCheck if the Simple Service Discovery Protocol (SSDP) feature is enabled on the router. This is typically found under Advanced or LAN settings in the web interface, or by sending a SSDP M-SEARCH request to the device on port 1900.Affected if SSDP is enabled and responding on the device.
-
Confirm web interface accessibilityAttempt to access the router's web interface on ports 80 (HTTP) or 443 (HTTPS) from the network. Use a browser or curl command: curl http://192.168.0.1 or the actual gateway IP.Affected if The web interface (cgibin endpoint) is accessible on the network.
The device is affected if it is a D-Link DIR-860L running firmware version 2.04.B04 with the SSDP service enabled and the web interface accessible on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedSince D-Link no longer supports this product and no official patch exists, replace the end-of-life device. If immediate replacement is not feasible, implement compensating controls such as firewall rules restricting access to the router's management interface to trusted IP addresses only, or disable SSDP if the feature is not required.
- 1. This vulnerability affects D-Link DIR-860L firmware 2.04.B04, which is explicitly stated as a product no longer supported by the maintainer.
- 2. D-Link has not released a patch or newer firmware version to address CVE-2025-9026 for this end-of-life device.
- 3. Replace the D-Link DIR-860L with a currently supported router from D-Link or another manufacturer that receives active security updates.
- 4. If immediate replacement is not possible, implement network segmentation to isolate the affected device on a restricted VLAN.
- 5. Block inbound SSDP (UDP port 1900) at the network perimeter firewall to prevent external attackers from reaching the vulnerable service.
- 6. Disable the Simple Service Discovery Protocol (SSDP) service on the device through the web interface if the option is available.
- 7. Monitor network traffic for signs of exploitation attempts targeting this vulnerability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9026 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9026 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data