CVE-2025-11423
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 found in Tenda CH22 1.0.0.1. This affects the function formSafeEmailFilter of the file /goform/SafeEmailFilter. Performing a manipulation of the argument page results in memory corruption. The attack is possible to be carried out remotely. The exploit has been made public and could 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 confidenceMemory corruption vulnerability in Tenda CH22 router web interface (firmware 1.0.0.1). The formSafeEmailFilter function in /goform/SafeEmailFilter does not properly validate the 'page' parameter, allowing an attacker to trigger memory corruption remotely. Public exploit 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 the device modelAccess the router admin panel or check the device label to confirm it is a Tenda CH22 router. Alternatively, use network scanning to identify the device manufacturer and model via HTTP headers or services.Affected if The device is not a Tenda CH22 router.
-
Check the firmware versionLog into the router web interface and navigate to the System Settings or Status page to view the firmware version. Alternatively, use the router's API or check the download page provided by Tenda for the device.Affected if The installed firmware version is exactly 1.0.0.1.
-
Verify the web interface is accessibleAttempt to access the router's web interface by navigating to its IP address (commonly 192.168.0.1 or 192.168.1.1) in a web browser. Confirm the login page loads.Affected if The web interface is exposed and accessible from the network.
-
Confirm the vulnerable endpoint existsSend an HTTP GET or POST request to http://<router-ip>/goform/SafeEmailFilter using a tool like curl or Burp Suite. Observe if the endpoint responds or returns any error messages.Affected if The /goform/SafeEmailFilter endpoint is reachable and responds to requests.
-
Check if SafeEmailFilter feature is enabledLog into the router admin panel and look for Email Filter, Safe Email Filter, or similar security filtering features in the web interface menus. Check if the feature can be configured or is currently active.Affected if The SafeEmailFilter feature is enabled or configurable on the device.
A user is affected if they are running Tenda CH22 firmware version 1.0.0.1 with the web interface accessible and the SafeEmailFilter feature present.
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 patch if available; if no patch exists, disable the web interface or replace the device. Implement network segmentation to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11423 — 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-11423 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