CVE-2026-15695
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 flaw has been found in Tenda BE12 Pro 16.03.66.23. The affected element is the function fromDhcpListClient of the file /goform/DhcpListClient. This manipulation of the argument page causes stack-based buffer overflow. The attack can be initiated remotely. The exploit has been published 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 confidenceStack-based buffer overflow in the DHCP client list handler of Tenda BE12 Pro routers (firmware 16.03.66.23). The fromDhcpListClient function in /goform/DhcpListClient does not properly validate the 'page' parameter before copying it to a stack buffer, allowing remote attackers to potentially execute arbitrary code via crafted HTTP requests.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Tenda BE12 Pro router modelCheck the router label or web interface for the exact model number (BE12 Pro)Affected if Device is not a Tenda BE12 Pro router - different models have different vulnerabilities
-
Check firmware versionLog into the router web interface, look for firmware version in System Settings or Status page, or query the device via SNMP or telnet if availableAffected if Firmware version is 16.03.66.23 - this is the specific version listed as vulnerable
-
Verify DhcpListClient endpoint existsSend an HTTP GET request to http://[router-ip]/goform/DhcpListClient and check for a responseAffected if The endpoint responds - indicates the vulnerable function is present on the device
-
Confirm 'page' parameter is acceptedSend a crafted HTTP POST or GET request to /goform/DhcpListClient with a 'page' parameter (e.g., page=test) and observe if the parameter is processed without validationAffected if The 'page' parameter is accepted and reflected in the response without input validation - indicates the vulnerability is present
-
Check network exposure of management interfaceDetermine if the router's web interface (port 80/443) is exposed to untrusted networks by reviewing firewall rules or performing a port scan from an external IPAffected if The management interface is directly accessible from untrusted networks (WAN) rather than only from trusted LAN segments
The device is affected if it is a Tenda BE12 Pro router running firmware version 16.03.66.23 with the /goform/DhcpListClient endpoint accessible and the 'page' parameter accepting unvalidated input.
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 dataIsolate the router's management interface from untrusted networks immediately. Contact Tenda for an official firmware patch. If no patch is available, implement compensating controls such as firewall rules restricting access to the web interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15695 — 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-2026-15695 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