CVE-2025-28220
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 W6_S v1.0.0.4_510 has a Buffer Overflow vulnerability in the setcfm function, which allows remote attackers to cause web server crash via parameter funcpara1 passed to the binary through a POST 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 buffer overflow vulnerability exists in the setcfm function of Tenda W6_S v1.0.0.4_510 firmware. Remote attackers can trigger a denial of service by sending a POST request with an overly large funcpara1 parameter, causing the web server to crash due to improper bounds checking.
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= 1.0.0.4\(510\)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 the device modelAccess the router web interface or check the device label to confirm it is a Tenda W6_S modelAffected if The device is not a Tenda W6_S unit
-
Check the firmware versionLog into the router admin panel and navigate to System Settings > Firmware Upgrade, or use the router's web UI to locate the firmware version information. Compare against 1.0.0.4(510)Affected if The installed firmware version is exactly 1.0.0.4(510)
-
Verify the web server is activeAttempt to access the router web interface on the default IP (usually 192.168.0.1 or 192.168.1.1) over HTTP/HTTPSAffected if The web interface is accessible and responds to requests
-
Check for the setcfm endpoint exposureSend a POST request to the router's web interface endpoint (commonly /goform/ or /cgi-bin/) targeting a setcfm function. Use a tool like curl: curl -X POST http://<router_ip>/goform/setcfm -d "funcpara1=<test_value>"Affected if The setcfm function accepts POST requests and returns a response without proper input validation errors
-
Test for vulnerability trigger conditionSend a POST request with an abnormally large funcpara1 parameter value (several kilobytes of data) to the setcfm endpoint and observe if the web server becomes unresponsive or crashesAffected if The web server crashes or becomes unresponsive after sending a large funcpara1 parameter value
A user is affected if they have a Tenda W6_S router running firmware version 1.0.0.4(510) with an accessible web interface where the setcfm function can be triggered with an oversized funcpara1 parameter.
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; if no update exists, implement input length validation on the funcpara1 parameter in the setcfm function or disable the affected web service endpoint.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28220 — 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-28220 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