dbcve.org
X15 FirmwareOperating system · Totolink

CVE-2025-5502

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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, which was classified as critical, has been found in TOTOLINK X15 1.0.0-B20230714.1105. Affected by this issue is the function formMapReboot of the file /boafrm/formMapReboot. The manipulation of the argument deviceMacAddr leads to command injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

A command injection vulnerability exists in TOTOLINK X15 router firmware version 1.0.0-B20230714.1105. The formMapReboot function in /boafrm/formMapReboot fails to sanitize the deviceMacAddr parameter, allowing remote attackers to execute arbitrary OS commands without authentication.

MitigationSince the vendor has not responded and no patch is available, immediately restrict the router's management interface to trusted networks only using firewall rules or disable WAN access. Monitor for signs of exploitation given the public exploit availability.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify the installed firmware version
    Access the router web interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to the Status or System Information page to view the firmware version. Alternatively, check the firmware file name or header if you have firmware dump access.
    Affected if The firmware version is exactly 1.0.0-B20230714.1105 (or the version string matches that build date)
  2. Verify the vulnerable formMapReboot endpoint exists
    Attempt to access the URI /boafrm/formMapReboot via HTTP POST request to the router's web interface. If the router responds (even with an error), the endpoint is present.
    Affected if The endpoint responds to requests, indicating the vulnerable firmware is running
  3. Confirm management interface accessibility
    Check router firewall settings via the web UI under Security or Firewall settings. Determine if the management web interface (port 80/443) is accessible from WAN/outside networks. Use an external host to test connectivity to the router's public IP on ports 80/443.
    Affected if Port 80 or 443 is open to the WAN (0.0.0.0/0) or untrusted networks in the firewall configuration
  4. Inspect for signs of compromise
    Review router logs for suspicious commands or unexpected reboots. Check for unfamiliar processes, modified configurations, or new admin accounts in the router settings. Look for indicators such as unexpected DNS changes, new port forwards, or unknown wireless clients.
    Affected if Logs show unexpected system commands, the configuration has been modified without admin action, or new unauthorized accounts exist

You are affected if your TOTOLINK X15 runs firmware version 1.0.0-B20230714.1105 AND the management interface is accessible from untrusted networks.

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

Since the vendor has not responded and no patch is available, immediately restrict the router's management interface to trusted networks only using firewall rules or disable WAN access. Monitor for signs of exploitation given the public exploit availability.

Fix this in X15 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5502 — 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-5502 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