Ch22 FirmwareOperating system · Tenda

CVE-2025-12232

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 detected in Tenda CH22 1.0.0.1. Affected by this vulnerability is the function fromSafeClientFilter of the file /goform/SafeClientFilter. Performing a manipulation of the argument page results in buffer overflow. The attack can be initiated remotely. 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 · high confidence

A buffer overflow vulnerability exists in the Tenda CH22 router firmware (version 1.0.0.1) in the /goform/SafeClientFilter endpoint. The fromSafeClientFilter function fails to properly validate the 'page' parameter before use, allowing an attacker to trigger a buffer overflow via a crafted HTTP request. The vulnerability is remotely exploitable without authentication and has a public exploit, making it critical for affected devices.

MitigationImmediately check for and apply any vendor firmware updates for the Tenda CH22. If no update is available, restrict network access to the device's web management interface using firewall rules or disable remote administration until a patch is released.

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
Ch22 FirmwareOperating system
Affected:= 1.0.0.1

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 checks

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

  1. Identify the router model
    Access the router's web interface or check the device label to confirm it is a Tenda CH22 model.
    Affected if The device is not a Tenda CH22 router, then it is not affected by this specific CVE.
  2. Check the firmware version
    Log into the router web interface and navigate to the System Settings or Firmware Upgrade page to view the current firmware version, or use the command 'cat /proc/version' via telnet/SSH if available.
    Affected if The firmware version is 1.0.0.1, then the device is running the affected version.
  3. Verify the vulnerable endpoint exists
    Send an HTTP GET request to 'http://<device_ip>/goform/SafeClientFilter' using a tool like curl or a browser. A valid response (even an error page) indicates the endpoint is present.
    Affected if The endpoint returns an HTTP response, indicating the SafeClientFilter handler is enabled on the device.
  4. Check if remote web management is enabled
    Check the router's Administration or Remote Management settings to see if remote access to the web interface is enabled. Look for options like 'Remote Management', 'Web Management', or 'HTTP/HTTPS Access' set to WAN/Internet.
    Affected if Remote management is enabled and the router is accessible from the WAN, then the vulnerability is remotely exploitable without authentication.

A Tenda CH22 router running firmware version 1.0.0.1 with the web management interface exposed to the network is affected by this buffer overflow vulnerability in the /goform/SafeClientFilter 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately check for and apply any vendor firmware updates for the Tenda CH22. If no update is available, restrict network access to the device's web management interface using firewall rules or disable remote administration until a patch is released.

Fix this in Ch22 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12232 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12232 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