CVE-2025-4896
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 AC10 16.03.10.13 and classified as critical. Affected by this issue is some unknown functionality of the file /goform/UserCongratulationsExec. The manipulation of the argument getuid leads to buffer overflow. The attack may be launched 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 · moderate confidenceA buffer overflow vulnerability exists in the Tenda AC10 router firmware 16.03.10.13 within the /goform/UserCongratulationsExec web interface function. The getuid parameter is not properly bounds-checked, allowing an attacker to overflow a buffer via crafted HTTP requests. This can be exploited remotely without authentication.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Tenda AC10 firmware versionAccess the router's web admin interface (typically at 192.168.0.1) and navigate to System Settings > Firmware Upgrade or System Status page. The firmware version is displayed there. Alternatively, check the firmware file name if you have a firmware backup, or use network enumeration to detect the device fingerprint.Affected if The displayed firmware version is 16.03.10.13
-
Confirm exact version matchVerify that the firmware version reads exactly 16.03.10.13. Note that other versions of the same router model may have different version numbers and may not be affected by this specific CVE.Affected if The version string is exactly 16.03.10.13 (no other version numbers)
-
Verify web interface is accessibleAttempt to access the router's login page at http://192.168.0.1/goform/UserCongratulationsExec or http://[router-ip]/goform/UserCongratulationsExec using a web browser or curl command.Affected if The web interface responds with any content (login page, error, or unexpected response), indicating the vulnerable function is present in the firmware
-
Check if remote management is enabled (optional context)In the router web admin interface, look for options like Remote Management, Remote Access, or WAN Access under Advanced Settings. Determine if the web interface is reachable from outside the local network.Affected if Remote management is enabled and the router is accessible from WAN, increasing exposure to remote exploitation
If the Tenda AC10 router is running firmware version exactly 16.03.10.13 and the web interface is accessible, the device is affected by CVE-2025-4896.
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; immediately restrict access to the router's web administration interface from untrusted networks or disable remote management if not required.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4896 — 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-4896 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