CVE-2025-5739
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 TOTOLINK X15 1.0.0-B20230714.1105. This affects an unknown part of the file /boafrm/formSaveConfig of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer overflow. It is possible to initiate 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 · moderate confidenceA buffer overflow vulnerability exists in TOTOLINK X15 router firmware (version 1.0.0-B20230714.1105) within the HTTP POST request handler for the /boafrm/formSaveConfig endpoint. The submit-url parameter is not properly validated before being used in a memory operation, allowing an attacker to overflow a buffer and potentially execute arbitrary code remotely.
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
- 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 device modelCheck if the router is a TOTOLINK X15 model. This may be visible on the device label, in the web interface header, or via SNMP/sysinfo queries.Affected if The device is not a TOTOLINK X15 model, then this specific CVE does not apply.
-
Determine the firmware versionAccess the router web interface or check via TFTP/SSH to retrieve the installed firmware version. Compare your installed version to 1.0.0-B20230714.1105.Affected if The installed firmware version is exactly 1.0.0-B20230714.1105.
-
Verify the web service is runningConfirm that the router HTTP/HTTPS web interface is accessible on the LAN or WAN interface. Attempt to reach the device login page.Affected if The web interface is not accessible, the vulnerable endpoint cannot be reached.
-
Confirm the vulnerable endpoint existsCheck if the /boafrm/formSaveConfig endpoint is present and accessible on the device by inspecting HTTP responses or attempting a test request to this path.Affected if The /boafrm/formSaveConfig endpoint is present and accepts the submit-url parameter.
You are affected if you have a TOTOLINK X15 router running firmware version 1.0.0-B20230714.1105 with the web interface accessible and the /boafrm/formSaveConfig endpoint functional.
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 dataImplement strict input validation and length checking on the submit-url parameter in the formSaveConfig function, or apply an official firmware patch from TOTOLINK if available. Consider deploying a web application firewall as a temporary mitigation.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5739 — 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-5739 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