/

CVE-2026-51659

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51659

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthenticated Sensitive 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 router allows unauthenticated users to retrieve DMZ configuration information through the getUrlFilterRules function.

The issue becomes risky when the management interface exposes the affected CGI endpoint and fails to enforce authentication before processing crafted POST requests.

Affected context

The vulnerability occurs in TOTOLINK T6 4.1.5cu.748_B20211015 deployments where the router's CGI management interface exposes the getUrlFilterRules function through /cgi-bin/cstecgi.cgi. Risk depends on whether this endpoint is reachable by an attacker and whether access checks are missing or inconsistently applied before DMZ-related configuration data is returned.

Exploit preconditions

  • Attack surface: The router's HTTP or CGI management interface
  • Required access: Network reachability to the affected endpoint; valid authentication may not be required
  • Trigger point: A crafted POST request processed by the getUrlFilterRules function
  • Why exploitation is possible: The function does not consistently enforce authorization before disclosing DMZ configuration information

Why this happens

The underlying issue is an authorization failure in an administrative CGI handler. The function exposes configuration data without first verifying that the requester has the necessary authenticated and authorized session context. This behavior maps to CWE-284: Improper Access Control, where access to a protected resource or operation is not adequately restricted.

Potential impact

  • An unauthenticated attacker may obtain DMZ configuration information
  • Exposed configuration details could reveal internal hosts, services, or network-management choices
  • The information could support follow-on attacks against devices or services behind the router
  • Organizations may experience loss of confidentiality for network configuration data

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every administrative endpoint and minimizing the information returned to unauthenticated callers.

Common defensive patterns include:

  • Requiring authenticated, authorized sessions before processing configuration queries
  • Applying centralized access-control checks consistently across CGI handlers
  • Returning only the minimum data required for the requesting operation
  • Restricting management interfaces to trusted networks or dedicated administration paths
  • Disabling remote management where it is not necessary
  • Using least-privilege administrative roles and separating read access from configuration-changing privileges
  • Treating all client-supplied request fields as untrusted and validating them server-side

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review checks for administrative handlers that return configuration data without a preceding authorization decision
  • Tests that call management endpoints with no session, expired sessions, and insufficient-privilege sessions
  • HTTP policy monitoring for unauthenticated requests to CGI configuration functions
  • API inventories that identify endpoints exposing network, firewall, DMZ, or routing information
  • Automated security testing that verifies both authentication and object-level authorization at each administrative operation

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 interface and affected CGI endpoint are reachable from an attacker's network. Exposure depends on deployment and remote-management settings.

The described flaw allows unauthenticated access to the affected function, so a valid administrative session may not be required.

Enforce authentication and authorization before executing the function or returning any DMZ configuration data, while limiting responses to the minimum necessary information.

Apply centralized access-control middleware, test endpoints with missing and low-privilege sessions, restrict management exposure, and monitor for unauthenticated requests to administrative CGI paths.

Find out what's already
exploitable in your codebase.