CVE-2026-36777
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 W3 Wireless Router v1.0.0.3(2204) was discovered to contain a stack overflow in the param_1 parameter of the formSetCfm 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 · moderate confidenceA stack buffer overflow vulnerability exists in the formSetCfm function of Tenda W3 Wireless Router firmware v1.0.0.3(2204). The vulnerability is caused by insufficient bounds checking on the param_1 parameter, allowing an attacker to send a crafted HTTP request that overwrites stack memory, leading to 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 device modelAccess the router web interface or check device label/marketing materials to confirm it is a Tenda W3 Wireless RouterAffected if Device is not a Tenda W3 model
-
Check firmware versionLog into the router web interface and navigate to System Settings or Status page to view the firmware version. Alternatively, check via CLI if telnet/ssh is enabled or inspect firmware binary if accessible.Affected if Firmware version is 1.0.0.3(2204)
-
Verify web management interface is accessibleAttempt to access the router's HTTP/HTTPS web interface on the default IP (commonly 192.168.0.1 or 192.168.1.1). Determine if the interface responds to login requests.Affected if Web management interface is reachable from network
-
Check remote administration exposureReview router settings for 'Remote Management', 'Remote Access', or 'Web Management' settings to determine if remote (WAN) access is enabled.Affected if Remote administration is enabled, exposing the web interface to WAN
-
Identify vulnerable formSetCfm endpointInspect HTTP requests to the router's formSetCfm function by reviewing router's web server logs or attempting a benign request to the form handler endpoint (commonly /goform/formSetCfm or similar).Affected if The formSetCfm handler is present and accessible
The device is affected if it is a Tenda W3 router running firmware version 1.0.0.3(2204) with the web management interface accessible to an attacker.
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 input validation and length checks on the param_1 parameter in the formSetCfm function; if available, update to a patched firmware version; otherwise, restrict administrative interface access to trusted networks to reduce attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36777 — 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-36777 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