CVE-2025-57085
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 · uneditedTenda W30E V16.01.0.19 (5037) was discovered to contain a stack overflow in the v17 parameter in the UploadCfg function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted 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 overflow vulnerability exists in the Tenda W30E router firmware version 16.01.0.19 (5037) within the UploadCfg function's v17 parameter. Attackers can send a crafted request with an oversized v17 value to overflow the stack, potentially allowing code execution or causing a denial of service. The CVSS 9.8 score indicates this is likely exploitable for remote code execution rather than just DoS.
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<= 16.01.0.19\(5037\)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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Tenda W30E firmware versionAccess the router web administration interface and navigate to System Settings > Firmware Version, or log in via SSH/Telnet and run 'cat /proc/version' or check /etc/version fileAffected if The installed firmware version is 16.01.0.19 (5037) or any version lower than this (e.g., 16.01.0.18, 15.x.x.x)
-
Confirm device model is W30ECheck the router label or web interface for the exact model numberAffected if The device is a Tenda W30E router (other Tenda models may have different affected version ranges)
-
Verify UploadCfg function accessibilityAttempt to access the UploadCfg endpoint via HTTP POST request to the router's management interface (commonly /cgi-bin/upload)Affected if The UploadCfg function is exposed and accepts requests without additional authentication barriers beyond standard web login
-
Check network exposure of management interfaceReview router firewall rules and determine if the web management interface (port 80/443) is accessible from untrusted networks or the internetAffected if The management interface is reachable from external/untrusted networks rather than only from trusted internal LAN segments
You are affected if you have a Tenda W30E router running firmware version 16.01.0.19 (5037) or lower, and the UploadCfg function is accessible either locally or from exposed network segments.
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 the latest vendor firmware update if available; if no patch exists, disable the UploadCfg function via access controls or restrict network exposure to trusted management interfaces only.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57085 — 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-2025-57085 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