CVE-2026-36792
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 wl_radio parameter of the formWifiRadioSet 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 confidenceStack overflow vulnerability in the wl_radio parameter of the formWifiRadioSet function in Tenda W3 Wireless Router v1.0.0.3(2204). An unauthenticated attacker can send a crafted HTTP request with an oversized wl_radio parameter to trigger the stack overflow, causing 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 device modelAccess the router's web interface or check the device label to confirm it is a Tenda W3 Wireless Router. Alternatively, inspect DHCP lease tables or network scans for Tenda W3 indicators.Affected if The device is a Tenda W3 Wireless Router.
-
Check firmware versionLog into the router's web interface and navigate to System Settings or Status page to view the firmware version. Alternatively, use the router's administration API or check the firmware file if extracted.Affected if The firmware version is 1.0.0.3(2204).
-
Confirm web interface accessibilityAttempt to access the router's HTTP management interface (typically on port 80 or 8080) from the network. Check if the login page responds.Affected if The router's web management interface is accessible from the network.
-
Test vulnerable endpoint availabilitySend an HTTP POST request to /goform/formWifiRadioSet with a wl_radio parameter containing an overly long string (e.g., 500+ characters). Observe if the request is accepted and processed.Affected if The formWifiRadioSet endpoint accepts requests with a wl_radio parameter.
A user is affected if they operate a Tenda W3 router on firmware version 1.0.0.3(2204) with an accessible web management interface that accepts the wl_radio parameter in the formWifiRadioSet function.
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 firmware update when available; otherwise, restrict access to the router's web management interface to trusted networks only or disable remote HTTP management.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36792 — 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-36792 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