CVE-2025-10440
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 has been found in D-Link DI-8100, DI-8100G, DI-8200, DI-8200G, DI-8003 and DI-8003G 16.07.26A1/17.12.20A1/19.12.10A1. Affected by this vulnerability is the function sub_4621DC of the file usb_paswd.asp of the component jhttpd. The manipulation of the argument hname leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
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 D-Link DI-8100, DI-8100G, DI-8200, DI-8200G, DI-8003, and DI-8003G routers. The jhttpd web server's usb_paswd.asp page contains function sub_4621DC which fails to sanitize the hname parameter before passing it to system shell execution, allowing remote attackers to execute arbitrary OS commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 device modelAccess the router's web administration interface or check the device label/marketing to confirm the exact model (DI-8100, DI-8100G, DI-8200, DI-8200G, DI-8003, or DI-8003G).Affected if The device model matches one of the listed affected models.
-
Check firmware versionLog into the router's web interface and navigate to the Status or System Information page to view the current firmware version. Alternatively, use the command line (if accessible) or check D-Link's support page for your model.Affected if The installed firmware version has not been patched by D-Link to address CVE-2025-10440 (no fixed version specified; compare to any available updates from D-Link).
-
Verify web interface accessibilityAttempt to reach the router's web interface (typically at the LAN IP or WAN IP if remote management is enabled) on ports 80 or 443.Affected if The jhttpd web server is reachable, making the vulnerable usb_paswd.asp page accessible.
-
Confirm vulnerable endpoint existsRequest the URL /usb_paswd.asp on the router's web server (e.g., http://<router-ip>/usb_paswd.asp).Affected if The page loads or responds, indicating the vulnerable endpoint is present on the device.
You are affected if your device is a D-Link DI-8100, DI-8100G, DI-8200, DI-8200G, DI-8003, or DI-8003G router with a web-accessible jhttpd server and the usb_paswd.asp endpoint is present.
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.
From vendor dataCheck D-Link support for available firmware updates addressing this vulnerability; if no patch exists, consider network segmentation to restrict access to the device's web interface or device replacement.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10440 — 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-10440 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