dbcve.org
X15 FirmwareOperating system · Totolink

CVE-2025-5786

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was found in TOTOLINK X15 1.0.0-B20230714.1105. It has been classified as critical. Affected is an unknown function of the file /boafrm/formDMZ of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to 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 confidence

Buffer overflow vulnerability in TOTOLINK X15 router firmware (v1.0.0-B20230714.1105) HTTP POST Request Handler for the formDMZ function. The 'submit-url' argument is not properly bounds-checked, allowing remote attackers to overflow a buffer via crafted HTTP POST requests to /boafrm/formDMZ.

MitigationApply vendor firmware patch when available; disable DMZ feature in router settings as temporary workaround; restrict access to router web interface to trusted networks/IPs.

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
X15 FirmwareOperating system
Affected:= 1.0.0-b20230714.1105

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed firmware version
    Access the router web interface and navigate to the System/Status or Firmware Upgrade page to view the current firmware version. Alternatively, check via CLI if telnet/ssh is enabled using 'nvram get firm_version' or similar command if available.
    Affected if The firmware version is exactly 1.0.0-b20230714.1105 (note: only this specific version is affected; other versions may have different statuses)
  2. Confirm the router has an accessible web management interface
    Attempt to access the router's IP address via HTTP/HTTPS on common ports (80/443) to verify the web interface is reachable.
    Affected if The web interface is accessible from the network segment being tested (the vulnerability is exploited via HTTP POST requests)
  3. Check if the formDMZ endpoint exists
    Send a GET request to /boafrm/formDMZ or attempt to access this path through the router's web interface to see if the handler is present.
    Affected if The /boafrm/formDMZ endpoint responds or is accessible (this indicates the vulnerable form handler is loaded)
  4. Determine if the DMZ feature is configurable or enabled
    Log into the router administrative interface and navigate to the DMZ settings page (usually under Firewall, NAT, or Advanced settings). Check whether DMZ can be configured or is currently enabled.
    Affected if The DMZ feature is present and configurable in the router firmware (the buffer overflow occurs in the formDMZ function handling)
  5. Verify the 'submit-url' parameter is accepted
    If authenticated, attempt to submit a request to /boafrm/formDMZ with the 'submit-url' parameter to confirm the parameter is processed by the firmware.
    Affected if The 'submit-url' parameter is accepted and processed by the formDMZ handler (this is the vulnerable parameter that lacks bounds checking)

A user is affected if the TOTOLINK X15 router is running firmware version 1.0.0-b20230714.1105 AND the web management interface with the /boafrm/formDMZ endpoint is accessible, as the buffer overflow occurs in the submit-url parameter handling of that specific firmware version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; disable DMZ feature in router settings as temporary workaround; restrict access to router web interface to trusted networks/IPs.

Fix this in X15 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5786 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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