CVE-2025-13400
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 · uneditedA vulnerability was detected in Tenda CH22 1.0.0.1. Affected is the function formWrlExtraGet of the file /goform/WrlExtraGet. Performing a manipulation of the argument chkHz results in buffer overflow. Remote exploitation of the attack is possible. The exploit is now public and may be used.
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 confidenceBuffer overflow vulnerability in Tenda CH22 router firmware 1.0.0.1. The formWrlExtraGet function in /goform/WrlExtraGet fails to properly validate the length of the chkHz parameter before copying it into a fixed-size buffer, allowing remote attackers to overflow the buffer and potentially achieve remote code execution.
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.1CVSS 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 device modelAccess the router web interface or check the device label/metadata to confirm the model is Tenda CH22Affected if Device is not a Tenda CH22 router (different models are not affected by this specific CVE)
-
Check firmware versionLog into the router admin panel (typically at 192.168.0.1) and navigate to System Settings > Firmware Upgrade, or use the command 'cat /proc/version' via telnet/SSH if available, to determine the installed firmware versionAffected if Firmware version is exactly 1.0.0.1 (this is the only affected version per vendor disclosure)
-
Verify vulnerable web endpoint existsSend an HTTP GET or POST request to http://[router-ip]/goform/WrlExtraGet using a tool like curl or a browser developer console. A 200 OK response or any server response (rather than a 404) indicates the endpoint is presentAffected if The /goform/WrlExtraGet endpoint returns a response (indicating the function is compiled into the firmware)
-
Test chkHz parameter handlingSend a POST request to /goform/WrlExtraGet with a crafted chkHz parameter containing an unusually long string (e.g., 200+ characters). Observe if the router hangs, crashes, or returns an error, or use a tool like Burp Suite to test for buffer overflow behaviorAffected if The router accepts unusually long chkHz input without rejecting it, or exhibits abnormal behavior (crash/restart) indicating the buffer is not properly validated
You are affected if you have a Tenda CH22 router running firmware version 1.0.0.1 with the /goform/WrlExtraGet endpoint accessible and the chkHz parameter accepting oversized input without validation.
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 if available; otherwise restrict access to the router's web management interface to trusted networks only, disable remote administration, and monitor for exploitation attempts given the public exploit availability.
- 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-13400 — 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-13400 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