Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-36813

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Shenzhen Tenda Technology Co., Ltd Tenda W15E v15.11.0.10 was discovered to contain a buffer overflow in the picCropName parameter of the formCropAndSetWewifiPic 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 confidence

A buffer overflow vulnerability exists in the Tenda W15E v15.11.0.10 router firmware in the picCropName parameter of the formCropAndSetWewifiPic function. An attacker can send a crafted HTTP request with an overly long string to overflow the buffer, causing the device to crash and resulting in a Denial of Service.

MitigationImplement strict input length validation on the picCropName parameter to enforce reasonable character limits before processing. As this is a firmware-level vulnerability, contact Tenda for an official firmware patch that properly bounds-checks the input.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the router admin panel or check via telnet/SSH. Look for system status or firmware version information typically found under 'System Status', 'Device Info', or 'Firmware Version' in the web UI. Alternatively, check the HTTP response headers or use Nmap with service detection to probe the web interface.
    Affected if The device is a Tenda W15E running firmware version v15.11.0.10 specifically.
  2. Confirm web management interface is accessible
    Attempt to reach the router's web interface via HTTP (typically on ports 80 or 8080). Use a browser or curl to access the login page. The vulnerability exists in the formCropAndSetWewifiPic function which is part of the web interface.
    Affected if The web management interface is exposed and reachable on the network.
  3. Verify wewifi feature is enabled
    Log into the router admin panel and look for 'Wewifi' or 'WiFi extension' features under Wireless or Advanced settings. The vulnerable function name 'formCropAndSetWewifiPic' suggests this feature must be active for the attack surface to exist.
    Affected if The Wewifi or similar picture cropping feature is enabled on the device.
  4. Check for abnormal device behavior
    Monitor the router for unexpected crashes, restarts, or unresponsive states. Review system logs if accessible via the admin panel under 'System Log' or 'Logs'. Look for signs of denial of service or unusual HTTP requests.
    Affected if The device has experienced unexplained crashes, restarts, or shows high CPU/memory usage after potential exploitation attempts.

You are affected if you are running a Tenda W15E router on firmware v15.11.0.10 with the web interface and wewifi feature accessible, and you observe device crashes or denial of service conditions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input length validation on the picCropName parameter to enforce reasonable character limits before processing. As this is a firmware-level vulnerability, contact Tenda for an official firmware patch that properly bounds-checks the input.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36813 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-36813 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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