CVE-2026-6631
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 determined in Tenda F451 1.0.0.7_cn_svn7958. Impacted is the function fromwebExcptypemanFilter of the file /goform/webExcptypemanFilter of the component httpd. Executing a manipulation of the argument page can lead to buffer overflow. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.
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 F451 router's httpd component. The fromwebExcptypemanFilter function in /goform/webExcptypemanFilter is vulnerable when processing the 'page' argument, allowing remote attackers to overflow a buffer. The exploit is publicly available and can be launched remotely without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 router modelAccess the router's web interface or check the device label to confirm it is a Tenda F451 router. Alternatively, check the HTTP Server header in responses or use network enumeration tools to identify the device.Affected if The device is a Tenda F451 router.
-
Check the firmware versionLog into the router admin panel and navigate to the System or Firmware section to view the installed firmware version. Compare this to any vendor advisories for fixed versions.Affected if The firmware version is older than the patched version or no patch is available.
-
Verify httpd service is runningScan the router's IP on common HTTP ports (80, 443, 8080) using a tool like curl or netcat to confirm the httpd service is listening and responding.Affected if The httpd service is running and accessible on the network.
-
Test access to the vulnerable endpointSend an HTTP GET or POST request to http://[router-ip]/goform/webExcptypemanFilter and verify the endpoint responds. Use a tool like curl: curl -v http://[router-ip]/goform/webExcptypemanFilterAffected if The endpoint responds with a valid HTTP response, indicating the vulnerable code path exists.
-
Check if remote administration is enabledIn the router admin panel, locate the Remote Management or Remote Access settings (often under Advanced or Administration). Verify whether remote access from WAN is permitted.Affected if Remote administration is enabled, allowing external attackers to reach the vulnerable endpoint.
A user is affected if they own a Tenda F451 router with the httpd service running, the /goform/webExcptypemanFilter endpoint accessible, and especially if remote administration is enabled, allowing unauthenticated remote exploitation.
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 when available; until then, restrict network access to the router's management interface or disable remote administration to reduce attack surface.
- Consultation4.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6631 — 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-2026-6631 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