/

CVE-2026-51642

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-284) in TOTOLINK T6 Mesh

CVE-2026-51642

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A broken access control vulnerability in the TOTOLINK T6 allows unauthenticated requests to retrieve mesh routing information through the getMeshRoutingTable function. An attacker who can reach the device's web interface may disclose internal mesh topology and routing details by sending a crafted POST request.

Affected context

The issue occurs in TOTOLINK T6 devices running firmware 4.1.5cu.748_B20211015 when the mesh routing table endpoint is exposed through the device's HTTP interface. Risk is higher when the management interface is reachable from untrusted networks and the function does not require valid authentication before returning routing information.

Exploit preconditions

  • Attack surface: The device's web management interface, specifically /cgi-bin/cstecgi.cgi
  • Required access: Network connectivity to the exposed HTTP endpoint; authentication may not be required
  • Trigger point: A crafted POST request invoking the getMeshRoutingTable function
  • Why exploitation is possible: The function does not adequately enforce authorization before disclosing mesh routing data

Why this happens

The underlying flaw is an authorization failure in a management function that exposes sensitive routing information without first verifying whether the requester is permitted to access it. This maps to CWE-284: Improper Access Control, where access restrictions are missing, inconsistent, or incorrectly applied to a protected resource.

Potential impact

  • An attacker may obtain mesh topology and routing information
  • Disclosure could help map connected nodes and network relationships
  • The exposed information could support reconnaissance for follow-on attacks
  • Network privacy and operational confidentiality could be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every management and diagnostic function that returns network information.

Common defensive patterns include:

  • Require authentication and explicit authorization before processing routing-table requests
  • Apply deny-by-default access controls to administrative endpoints
  • Limit management interfaces to trusted administration networks
  • Return only the minimum routing information necessary for an authorized operation
  • Separate diagnostic data from publicly reachable request handlers
  • Run device management services with narrowly scoped privileges where architecture permits
  • Treat all endpoint parameters and function selectors as untrusted input

How teams detect issues like this

Detection can include:

  • Static analysis and endpoint audits for handlers that return sensitive data without authorization checks
  • Code review searches for management functions whose authentication checks occur after data retrieval
  • Dynamic testing of administrative endpoints with unauthenticated and low-privilege requests
  • Web server and device logs reviewed for unusual POST requests to /cgi-bin/cstecgi.cgi
  • Policy enforcement requiring authentication and authorization coverage for all diagnostic API functions
  • Automated security testing tools that identify access-control differences between authenticated and unauthenticated requests

Sources

SourceLink
github.comgithub.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md
github.comgithub.com/ShengWu00/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md
totolink.nettotolink.net/
totolink.nettotolink.net/home/menu/detail/menu_listtpl/download/id/190/ids/36.html

Frequently asked

questions

It may be remotely exploitable when the device's management interface is reachable by an attacker. Exploitation does not necessarily require a valid account because the affected function may accept unauthenticated requests.

The function may disclose mesh routing information, including details that help an attacker understand connected nodes and network relationships.

The endpoint should enforce authentication and authorization before invoking the routing-table function or returning any routing data, while applying least-privilege access rules.

Require authorization checks for every sensitive API operation, test endpoints under multiple privilege levels, restrict management interfaces to trusted networks, and monitor requests for anomalous access patterns.

Find out what's already
exploitable in your codebase.