CVE-2025-8178
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 classified as critical has been found in Tenda AC10 16.03.10.13. Affected is an unknown function of the file /goform/RequestsProcessLaid. The manipulation of the argument device1D leads to heap-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the 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 confidenceHeap-based buffer overflow in Tenda AC10 router firmware 16.03.10.13 in the /goform/RequestsProcessLaid endpoint. The 'device1D' parameter is copied to a heap buffer without bounds checking, allowing remote attackers to overwrite adjacent memory and potentially achieve remote code execution.
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.13CVSS 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 administration interface (typically at 192.168.0.1) or check the device label/packaging to confirm the model is Tenda AC10.Affected if The device is NOT a Tenda AC10 router.
-
Check the installed firmware versionLog into the router web interface and navigate to System Settings > Firmware Upgrade or System Status page. Record the firmware version displayed.Affected if The firmware version is exactly 16.03.10.13.
-
Verify web management interface accessibilityAttempt to access the router's web interface from a network location outside your local LAN (e.g., using the router's WAN/public IP). Check if port 80 or 443 is open on the WAN interface.Affected if The router's web management interface is accessible from the WAN/internet.
-
Confirm the vulnerable endpoint existsSend an HTTP POST request to http://[router-ip]/goform/RequestsProcessLaid with a device1D parameter (e.g., device1D=test). A response (even an error) indicates the endpoint is active.Affected if The /goform/RequestsProcessLaid endpoint responds to requests with the device1D parameter.
You are affected if you have a Tenda AC10 router running firmware version 16.03.10.13 with the web interface network-accessible.
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 dataSince this is a firmware vulnerability in end-of-life consumer hardware with no vendor patch available, the primary remediation is network isolation (place device behind a firewall with no WAN exposure) or device replacement. If the router's remote management interface is accessible from WAN, disable it immediately.
- Consultation2.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 $1,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8178 — 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-8178 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