CVE-2026-36818
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 · uneditedShenzhen Tenda Technology Co., Ltd Tenda W20E v15.11.0.6 was discovered to contain a buffer overflow in the wewifiWhiteUserInfo parameter of the formAddWewifiWhiteUser function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.
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 confidenceA buffer overflow vulnerability exists in the Tenda W20E router firmware v15.11.0.6 within the formAddWewifiWhiteUser function's wewifiWhiteUserInfo parameter. Attackers can send a specially crafted HTTP request with oversized input to trigger the overflow, causing the device to crash and resulting in Denial of Service.
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
- 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 firmware versionAccess the router admin web interface (typically at 192.168.0.1) and navigate to System Settings > Firmware Version, or log in via telnet/SSH and run 'cat /proc/version' or 'cat /etc/os-release' to retrieve the firmware build numberAffected if The firmware version is v15.11.0.6 exactly, or falls within an unpatched version range that contains this build
-
Confirm the specific affected function existsCheck if the /goform/formAddWewifiWhiteUser endpoint is present on the router's web server by reviewing the firmware's web server binary or by attempting a request to that endpoint (if accessible)Affected if The formAddWewifiWhiteUser function is present in the firmware binary
-
Verify wewifi (guest WiFi) feature is enabledLog into the router admin panel and check if Guest WiFi (wewifi) is enabled under Wireless Settings > Guest WiFi, or inspect the router's configuration file for wewifi settingsAffected if The Guest WiFi (wewifi) feature is enabled and the white user list management function is accessible
-
Determine web interface exposureCheck if the router's HTTP/HTTPS management interface is reachable from the WAN (internet) side by reviewing port forwarding rules, remote management settings, or scanning the public IP for port 80/443Affected if The router's web management interface is exposed to untrusted network segments or the WAN interface
You are affected if your Tenda W20E runs firmware v15.11.0.6 (or an unpatched version) AND the guest WiFi feature is enabled AND the management interface is accessible to untrusted attackers.
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 vendor-supplied firmware updates when available; until then, restrict administrative web interface access to trusted networks or disable the wewifi white user feature if not needed.
- Consultation2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36818 — 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-36818 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