CVE-2025-12273
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 weakness has been identified in Tenda CH22 1.0.0.1. Affected is the function fromwebExcptypemanFilter of the file /goform/webExcptypemanFilter. Executing a manipulation of the argument page can lead to buffer overflow. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.
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 allows remote attackers to execute arbitrary code via the web interface by overflowing the 'page' argument in the /goform/webExcptypemanFilter endpoint. The fromwebExcptypemanFilter function lacks proper bounds checking on user-supplied input before copying to a fixed-size buffer.
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 the device modelAccess the router web interface or check the device label 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 the firmware versionLog into the router web interface and navigate to System Settings or Status page to view the firmware version, or use the command 'cat /proc/version' or 'cat /etc/firmware_version' via telnet/SSH if availableAffected if Firmware version is 1.0.0.1 - this is the only version listed as affected by this CVE
-
Determine if the web management interface is enabledAccess the router admin panel typically at http://192.168.0.1 or check via router status page for web interface statusAffected if Web interface is enabled and accessible - the vulnerability is exploitable through the web interface; if it is disabled, the attack surface is reduced but the vulnerable code may still exist in the firmware
-
Verify network exposure of the routerCheck router WAN IP address and firewall rules to determine if the web interface is accessible from the internet or only from the local networkAffected if The router web interface is exposed to the internet (WAN accessible) - remote exploitation requires network access to the web interface
You are affected if you have a Tenda CH22 router running firmware version 1.0.0.1 with the web interface enabled and accessible, regardless of whether it is LAN or WAN accessible, since the vulnerable code exists in that specific firmware version.
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; until then, isolate the device on a restricted network segment, disable remote web management if possible, and monitor for exploitation attempts given the publicly available exploit.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12273 — 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-12273 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