CVE-2025-50665
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 input parameters in the /web_keyword.asp endpoint. An attacker can exploit this vulnerability by sending a crafted HTTP GET request via the name, en, time, mem_gb2312, and mem_utf8 parameters.
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 version 16.07.26A1. The flaw is in the /web_keyword.asp web interface endpoint where the parameters name, en, time, mem_gb2312, and mem_utf8 fail to properly validate input length before copying data into fixed-size buffers. An attacker can exploit this by sending crafted HTTP GET requests with oversized payloads in these parameters, potentially causing denial of service or potentially executing arbitrary code.
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 router model and firmware versionAccess the D-Link DI-8003 web management interface by navigating to the router's IP address (typically 192.168.0.1). Look for a 'System' or 'Status' page that displays the firmware version. Alternatively, check via CLI through telnet or SSH if enabled.Affected if The firmware version displayed is exactly 16.07.26A1
-
Confirm the web management interface is activeAttempt to access http://<router-ip>/web_keyword.asp in a web browser. A successful HTTP response (even an error page) indicates the web interface is running.Affected if The /web_keyword.asp endpoint responds to HTTP requests, meaning the web management feature is enabled
-
Check if remote management access is permittedIn the router's web interface, navigate to the 'Management' or 'Access Control' settings. Look for options labeled 'Remote Management', 'Web Access', or 'HTTP Access' to see if remote (WAN) access is enabled.Affected if Remote management/WAN access to the web interface is enabled, exposing the vulnerable endpoint to external attackers
The device is affected if it runs firmware version 16.07.26A1 and the /web_keyword.asp endpoint is accessible, especially from remote networks.
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 dataUpdate to a patched firmware version if available from D-Link, or implement web application firewall rules to filter oversized input to the affected endpoint; if no firmware update is forthcoming, consider network segmentation or disabling the web interface to reduce exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50665 — 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-50665 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