CVE-2025-12271
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 identified in Tenda CH22 1.0.0.1. This affects the function fromRouteStatic of the file /goform/RouteStatic. Such manipulation of the argument page leads to buffer overflow. The attack can be launched remotely. The exploit is publicly available and might 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 · high confidenceA buffer overflow vulnerability exists in the Tenda CH22 router firmware version 1.0.0.1, specifically in the fromRouteStatic function within the /goform/RouteStatic endpoint. The page parameter is not properly bounds-checked, allowing an attacker to overflow the buffer by supplying an overly long string. This can be exploited remotely without authentication, and a public exploit is available.
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 router firmware versionAccess the router web interface and navigate to System Settings > Firmware Upgrade, or check the administration page for the firmware version. Alternatively, use the router's serial console or SSH if available to retrieve the version from system information.Affected if The displayed firmware version is exactly 1.0.0.1 (the only affected version listed)
-
Confirm the web interface is accessibleAttempt to access the router's IP address via HTTP/HTTPS in a web browser. The router login page should be reachable.Affected if The web interface is reachable from the network being tested (LAN or WAN)
-
Verify the RouteStatic endpoint existsSend an HTTP GET or POST request to http://[router-ip]/goform/RouteStatic and observe the response. A valid response indicates the endpoint is present.Affected if The endpoint responds (even with an error) indicating the vulnerable function exists on the device
-
Check if remote WAN access is enabledIn the router web interface, navigate to Advanced Settings > Remote Management or WAN Management. Verify whether remote administration/access is enabled for the WAN interface.Affected if Remote WAN management or web interface access from WAN is enabled, allowing unauthenticated remote exploitation
The device is affected if the firmware version is exactly 1.0.0.1 and the /goform/RouteStatic endpoint is accessible (especially from WAN), since the buffer overflow in the page parameter can then be exploited remotely without authentication.
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-supplied firmware updates immediately if available; otherwise restrict remote access to the router's web interface via firewall rules or disable WAN management access until a patch can be applied.
- Consultation3.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12271 — 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-12271 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