CVE-2025-5788
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 TOTOLINK X15 1.0.0-B20230714.1105. It has been rated as critical. Affected by this issue is some unknown functionality of the file /boafrm/formReflashClientTbl of the component HTTP POST Request Handler. The manipulation of the argument submit-url 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 confidenceBuffer overflow vulnerability in TOTOLINK X15 router firmware (v1.0.0-B20230714.1105) in the HTTP POST handler for /boafrm/formReflashClientTbl. The submit-url parameter is not properly bounds-checked, allowing remote attackers to overflow a buffer via crafted HTTP POST 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= 1.0.0-b20230714.1105CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the router modelAccess the router's web administration interface or check the device label/marketing to confirm the model is TOTOLINK X15Affected if The device is not a TOTOLINK X15 router, then it is not affected by this specific CVE
-
Check the installed firmware versionLog into the router's web interface and navigate to the firmware/version information page, or use the router's administrative CLI if available, to retrieve the exact firmware version stringAffected if The firmware version is NOT exactly 1.0.0-B20230714.1105 (note: capitalization and exact build string matter), then it is not affected by this CVE
-
Verify the vulnerable web handler existsSend an HTTP GET request to the router's IP address for the path /boafrm/formReflashClientTbl and confirm the endpoint responds (even if with an error or authentication prompt)Affected if The /boafrm/formReflashClientTbl endpoint does not exist or does not respond, the specific buffer overflow vulnerability cannot be triggered
-
Confirm the web interface is enabled and network-accessibleAttempt to access the router's HTTP (port 80) or HTTPS (port 443) web interface from the network segment where the router is deployedAffected if The web administration interface is disabled or completely unreachable, the attack surface for this HTTP-based buffer overflow does not exist
The environment is affected only if it is a TOTOLINK X15 router running exactly firmware version 1.0.0-B20230714.1105, the web interface is enabled, and the /boafrm/formReflashClientTbl CGI handler is present and 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 dataCheck TOTOLINK for available firmware updates; if none available, consider replacing the device as it may be end-of-life. Restrict administrative access to the router's web interface to trusted IPs only as a temporary workaround.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5788 — 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-5788 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