/

CVE-2026-51641

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51641

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized 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 high-severity access control flaw in the TOTOLINK T6 WiFi mesh configuration handler allows unauthenticated requests to retrieve mesh configuration and runtime state information. The issue becomes risky when the affected management endpoint is reachable by an attacker and does not require successful authentication before processing the request.

Affected context

The vulnerability occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 firmware, specifically in the getWiFiMeshConfig function exposed through /cgi-bin/cstecgi.cgi. Deployments are at greater risk when the device's management interface is reachable from an untrusted network and the endpoint does not consistently enforce authentication and authorization checks.

Exploit preconditions

  • Attack surface: HTTP POST request to the device's CGI management interface
  • Required access: Network reachability to the affected endpoint; authentication may not be required
  • Trigger point: Processing of a crafted request targeting the WiFi mesh configuration handler
  • Why exploitation is possible: The handler does not adequately verify that the requester is authorized to access mesh configuration and runtime state data

Why this happens

The underlying bug is an authorization failure in a management API. The getWiFiMeshConfig function exposes sensitive device information without reliably enforcing the access decision required for that operation. This maps to CWE-284: Improper Access Control, in which a protected resource or function is available to an actor who has not met the required security policy.

Potential impact

  • An unauthenticated attacker may obtain WiFi mesh configuration details
  • Exposed runtime state may help an attacker profile the device or network
  • Retrieved information could support follow-on attacks against administration interfaces
  • Disclosure may weaken network confidentiality and operational security

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every sensitive management endpoint and reducing exposure of device administration services.

Common defensive patterns include:

  • Requiring authentication and appropriate authorization before returning mesh configuration or runtime state
  • Applying centralized access-control checks consistently across CGI handlers
  • Limiting management interfaces to trusted administrative networks
  • Returning only the minimum data required for the requesting operation
  • Using secure-by-default network exposure and administrative access policies
  • Separating read-only diagnostics from configuration and privileged operations

How teams detect issues like this

Organizations can look for this issue through:

  • Dynamic testing of management endpoints with authenticated and unauthenticated requests
  • API inventory reviews that identify handlers returning configuration or runtime state
  • Code review checks for missing authentication or authorization calls before sensitive data access
  • Static analysis rules that flag direct response paths from administrative handlers without policy enforcement
  • Network monitoring for unusual requests to CGI management endpoints and repeated unauthenticated enumeration attempts
  • Automated security testing tools that verify authorization decisions across endpoint and role combinations

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 CGI management interface is reachable over a network controlled or observable by an attacker. Exploitability depends on network exposure and any additional access controls.

The described flaw permits unauthenticated access to the affected function, so valid credentials may not be required when the endpoint is reachable.

Enforce authentication and operation-specific authorization before processing the mesh configuration request or returning runtime state, while minimizing the information exposed in responses.

Apply centralized authorization policies to all management APIs, keep administrative interfaces off untrusted networks, test unauthenticated and low-privilege access paths, and monitor for unexpected endpoint use.

Find out what's already
exploitable in your codebase.