dbcve.org
W30e FirmwareOperating system · Tenda

CVE-2024-3881

HIGH · 8.8 CVSS v3.1 Published 2024-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability was found in Tenda W30E 1.0.1.25(633) and classified as critical. This issue affects the function frmL7PlotForm of the file /goform/frmL7ProtForm. The manipulation of the argument page leads to stack-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-260915. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

A stack-based buffer overflow vulnerability exists in the Tenda W30E router firmware version 1.0.1.25(633), specifically in the frmL7PlotForm function within /goform/frmL7ProtForm. The 'page' parameter is not properly validated before being used in a stack buffer, allowing remote attackers to potentially execute arbitrary code by sending specially crafted HTTP requests to the web management interface.

MitigationApply any vendor firmware update when available; until then, disable remote web management access, restrict network access to the management interface via firewall rules, or consider replacing the affected device if no patch is forthcoming.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
W30e FirmwareOperating system
Affected:= 1.0.1.25\(633\)

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 checks

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

  1. Identify Tenda W30E firmware version
    Log into the router web management interface and navigate to System Settings > Firmware Upgrade, or check the device label/box for the firmware version. Alternatively, use Nmap or curl to probe the device and attempt to retrieve version information from HTTP responses or SNMP if available.
    Affected if The installed firmware version matches exactly 1.0.1.25(633)
  2. Verify web management interface accessibility
    Determine if the router's web interface (typically on ports 80 or 443) is reachable from outside the local network. Check router firewall settings, WAN access restrictions, or perform an external port scan against the router's public IP address on ports 80/443.
    Affected if The web management interface is accessible from untrusted networks (WAN side)
  3. Confirm vulnerable endpoint exists
    Send a crafted HTTP GET or POST request to /goform/frmL7ProtForm with a test parameter. For example: curl -X POST http://<router_ip>/goform/frmL7ProtForm -d "page=test". Observe if the device responds or processes the request.
    Affected if The device responds to requests at the /goform/frmL7ProtForm endpoint and processes the 'page' parameter without error or sanitization

A user is affected if the Tenda W30E firmware is exactly version 1.0.1.25(633) and the web management interface is accessible (especially from WAN), allowing attackers to send malicious requests to the vulnerable /goform/frmL7ProtForm endpoint.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any vendor firmware update when available; until then, disable remote web management access, restrict network access to the management interface via firewall rules, or consider replacing the affected device if no patch is forthcoming.

Recommended fix High confidence
  1. No vendor-provided fix is available for this vulnerability.
  2. The vendor (Tenda) was contacted but did not respond to the disclosure.
  3. Consider the following workarounds:
  4. 1. Restrict network access to the device's web interface to trusted IP addresses only using firewall rules.
  5. 2. Disable remote management if not strictly necessary.
  6. 3. Monitor for indicators of compromise since the exploit is publicly available.
  7. 4. Evaluate replacement with alternative hardware that receives active security support.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in W30e Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-3881 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