/

CVE-2026-51672

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51672

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthenticated Information Disclosure

Severity:

CRITICAL RISK

(9.1)

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

An incorrect access-control check in the TOTOLINK T6 router's getRoamingCfg function exposes the device's roaming enablement status through a CGI endpoint. Because the endpoint may accept requests without authentication, a remote attacker could retrieve this configuration information by submitting a specially formed POST request.

Affected context

The issue occurs in TOTOLINK T6 devices using the affected firmware and handling requests through /cgi-bin/cstecgi.cgi. It becomes risky when the getRoamingCfg function is reachable over a network and does not consistently require authentication or enforce authorization before returning configuration data.

Exploit preconditions

  • Attack surface: The router's CGI web-management interface
  • Required access: Network connectivity to the affected endpoint; valid authentication may not be required
  • Trigger point: Processing of a request routed to the getRoamingCfg function
  • Why exploitation is possible: The function can return roaming configuration information without adequately verifying the caller's authorization

Why this happens

The underlying bug is an authorization failure in a management API. The function exposes configuration data based on request handling without applying a reliable authentication and authorization decision for the requested resource. This behavior maps to CWE-284: Improper Access Control, where access restrictions are missing, incomplete, or incorrectly enforced.

Potential impact

  • An unauthenticated attacker may learn whether roaming is enabled
  • The disclosed setting could support device or network reconnaissance
  • Repeated exposure of management information could weaken the router's security posture
  • The issue could be combined with other router vulnerabilities to improve attack planning

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every management endpoint and treating configuration responses as protected data.

Common defensive patterns include:

  • Require authentication and authorization before processing configuration queries
  • Apply centralized access-control checks consistently across CGI handlers
  • Default management interfaces to restricted network exposure
  • Separate public status data from administrative configuration data
  • Return minimal information when a caller is unauthorized
  • Use least-privilege management roles and secure administrative session controls
  • Monitor and restrict unexpected access to router management endpoints

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying CGI handlers that return configuration data without authorization checks
  • Code review signals such as endpoint-specific permission logic, missing session validation, or direct use of request parameters to select administrative functions
  • Dynamic testing that verifies unauthenticated and low-privilege requests receive consistent denial responses
  • Web-server and router logs showing repeated requests to management CGI paths from untrusted networks
  • Policy enforcement requiring authenticated access for all administrative API routes

Automated security testing and code-review tools may help identify inconsistent access-control enforcement.

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 router's management CGI interface is reachable by an attacker and the affected function accepts unauthenticated requests.

The attacker generally needs network connectivity to the router's exposed management endpoint. The described issue does not require a valid account when authorization is incorrectly enforced.

Require authentication and resource-level authorization before returning roaming or other administrative configuration data, while exposing only the minimum necessary response information.

Apply centralized access-control middleware, test every management endpoint with authenticated and unauthenticated roles, restrict management interfaces to trusted networks, and review logs for unauthorized access attempts.

Find out what's already
exploitable in your codebase.