CVE-2025-50667
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 buffer overflow vulnerability exists in D-Link DI-8003 16.07.26A1 due to improper handling of the iface parameter in the /wan_line_detection.asp endpoint.
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 · moderate confidenceA buffer overflow vulnerability exists in D-Link DI-8003 router firmware 16.07.26A1 within the /wan_line_detection.asp web endpoint. The iface parameter is not properly validated, allowing an attacker to overflow a buffer via crafted input.
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= 16.07.26a1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 it is a D-Link DI-8003 router.Affected if The device is not a D-Link DI-8003 model.
-
Check the firmware versionAccess the router admin panel, typically at 192.168.0.1, and navigate to Status or System Info page to view the firmware version. Alternatively, check the admin page for a version display in the footer or status section.Affected if The firmware version is exactly 16.07.26a1.
-
Verify the web interface is activeAttempt to access the router web interface over HTTP or HTTPS on the local network.Affected if The web management interface is not accessible or has been disabled.
-
Confirm vulnerable endpoint existsAttempt to access the URL path /wan_line_detection.asp on the router (e.g., http://192.168.0.1/wan_line_detection.asp). A 404 or access denied response indicates the endpoint may not exist or has been removed.Affected if The /wan_line_detection.asp endpoint is present and responds (other than 404).
You are affected if your D-Link DI-8003 router runs firmware version 16.07.26a1 and the /wan_line_detection.asp endpoint is accessible on your 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.
From vendor dataApply available firmware updates from D-Link. Until a patch is released, restrict access to the management interface via firewall rules or disable remote administration.
- Consultation2.0 h
- Testing5.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,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50667 — 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-50667 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