/

CVE-2026-51658

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51658

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Disclosure of Network Configuration

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 may allow unauthenticated users to retrieve DMZ configuration information through the device's CGI interface. The issue becomes risky when the management endpoint is reachable by an attacker and does not adequately enforce authorization before returning configuration data.

Affected context

The vulnerability occurs in the getDmzCfg function of TOTOLINK T6 firmware 4.1.5cu.748_B20211015. Deployments may be exposed when the device's CGI management interface is reachable from an attacker-controlled network and the endpoint does not consistently require authenticated access before processing configuration requests.

Exploit preconditions

  • Attack surface: The router's CGI management interface, particularly /cgi-bin/cstecgi.cgi
  • Required access: Network connectivity to the affected endpoint; authentication may not be required
  • Trigger point: A request handled by the getDmzCfg function
  • Why exploitation is possible: Authorization checks may be missing or insufficient before DMZ configuration data is returned

Why this happens

The underlying bug is an authorization design failure in which a sensitive configuration retrieval operation does not reliably verify the requester's privileges. This maps to CWE-284: Improper Access Control, because access to protected router configuration data is governed by incomplete or ineffective authorization enforcement.

Potential impact

  • An attacker may obtain DMZ and network exposure details
  • Exposed configuration data could help identify forwarded services or internal hosts
  • The information may support follow-on attacks against devices or services behind the router
  • Network security posture and administrative privacy could be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently at the server-side boundary for every sensitive management operation.

Common defensive patterns include:

  • Requiring authenticated, authorized sessions before returning DMZ configuration data
  • Applying deny-by-default access controls to management endpoints
  • Separating read and administrative privileges using least-privilege roles
  • Restricting management interfaces to trusted networks or administrative channels
  • Avoiding disclosure of sensitive configuration details in unauthenticated responses
  • Invalidating sessions appropriately and applying secure defaults for remote management

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for configuration handlers without centralized authorization enforcement
  • Tests that request sensitive CGI operations without credentials and verify that access is denied
  • API and firmware security assessments covering authentication, authorization, and information disclosure
  • Network monitoring for unauthenticated requests to router management endpoints
  • Policy enforcement requiring all management APIs to use a shared authentication and authorization layer

Automated security testing tools may help identify exposed administrative endpoints and inconsistent access-control behavior.

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 exploitable over the network when the affected CGI management endpoint is reachable by an attacker. Exposure depends on network placement, management-interface settings, and filtering controls.

The reported issue concerns unauthenticated access, so valid credentials may not be required when the endpoint is accessible and the authorization weakness is present.

Enforce authentication and authorization before processing sensitive configuration requests, using deny-by-default controls and least-privilege administrative roles.

Apply centralized access-control middleware to management APIs, test unauthenticated and low-privilege request paths, restrict administrative interfaces to trusted networks, and monitor unexpected access to configuration endpoints.

Find out what's already
exploitable in your codebase.