CVE-2025-57219
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 · uneditedIncorrect access control in the endpoint /goform/ate of Tenda AC10 v4.0 firmware v16.03.10.09_multi_TDE01 allows attackers to escalate privileges or access sensitive components via a crafted request.
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 confidenceTenda AC10 v4.0 router firmware v16.03.10.09 contains an incorrect access control vulnerability in the /goform/ate endpoint. This endpoint, likely intended for manufacturing test or调试 (debug) functions, does not properly enforce authorization checks, allowing authenticated or possibly unauthenticated attackers to escalate privileges or access sensitive router components via crafted requests.
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= 16.03.10.09_multi_tde01CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 modelLog into the router web interface or check the device label to confirm it is a Tenda AC10 model. This vulnerability only affects the AC10 hardware line.Affected if The device is not a Tenda AC10 router.
-
Check the installed firmware versionAccess the router administration panel, typically at 192.168.0.1, and navigate to System Settings or Firmware Upgrade to view the current firmware version. Alternatively, check the firmware file name if you have access to the router filesystem.Affected if The firmware version is exactly 16.03.10.09_multi_tde01, as this is the only confirmed affected version.
-
Verify the /goform/ate endpoint is reachableSend an HTTP GET or POST request to http://<router-ip>/goform/ate using a tool like curl or a browser. A response (even an error) indicates the endpoint exists and may be accessible.Affected if The endpoint responds, confirming it is exposed on the device.
-
Check network exposure of the management interfaceDetermine if the router web interface (port 80/443) is accessible from untrusted networks such as the public internet or a guest WiFi network. Use external port scanning tools or review firewall rules.Affected if The management interface is exposed to untrusted networks, increasing the risk of unauthenticated or low-privilege attackers reaching the vulnerable endpoint.
A user is affected if they own a Tenda AC10 router running firmware version 16.03.10.09_multi_tde01 with the /goform/ate endpoint accessible, especially if the management interface is exposed beyond trusted networks.
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 the vendor-supplied firmware patch for CVE-2025-57219 when available. If immediate patching is not possible, restrict network access to the router's management interface and monitor for unauthorized use of the /goform/ate endpoint.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57219 — 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-57219 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