/

CVE-2026-51620

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51620

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 broken access control vulnerability in the TOTOLINK T6 router allows unauthenticated attackers to retrieve network topology and interface configuration information through the getNetInfoCfg function. The issue becomes risky when the management endpoint accepts crafted requests without verifying that the requester has the required privileges.

Affected context

The vulnerability occurs in TOTOLINK T6 4.1.5cu.748_B20211015 deployments where the cgi-bin/cstecgi.cgi management endpoint exposes the getNetInfoCfg functionality without effective authentication or authorization checks. Devices that make this endpoint reachable to untrusted networks may have a broader exposure than devices restricted to a trusted administration network.

Exploit preconditions

  • Attack surface: The router's HTTP management interface, specifically the /cgi-bin/cstecgi.cgi endpoint
  • Required access: Network connectivity to the exposed management endpoint; authentication may not be required
  • Trigger point: A crafted POST request invoking the getNetInfoCfg function
  • Why exploitation is possible: The function returns network topology and interface configuration data without sufficiently checking the requester's authorization

Why this happens

The underlying flaw is an authorization design failure in which a sensitive information-returning function is reachable without a reliable privilege check. This behavior maps to CWE-284, Improper Access Control, because the application does not consistently enforce the intended trust boundary before processing the request and disclosing configuration data.

Potential impact

  • An attacker may learn network topology and interface configuration details.
  • The disclosed information could enable more targeted attacks against the router or connected systems.
  • Attackers could use the data to identify internal addressing, interfaces, or deployment characteristics.
  • Exposure of management information could increase the effectiveness of reconnaissance and lateral-movement attempts.

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every sensitive

management function rather than relying on endpoint obscurity or network

placement alone.

Common defensive patterns include:

  • Require authentication and explicit authorization before returning network or interface configuration data.
  • Apply deny-by-default access controls to diagnostic and information-disclosure functions.
  • Restrict management interfaces to trusted administration networks or approved administrative hosts.
  • Return only the minimum data needed for an authorized operation.
  • Separate read-only diagnostic privileges from broader router-administration privileges.
  • Use secure-by-default management settings and disable unnecessary external management exposure.

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static and dynamic analysis that identifies sensitive handlers without authentication or authorization checks.
  • Code review signals such as direct access to configuration-returning functions from general request dispatchers.
  • API and endpoint inventories that classify topology, interface, and diagnostic data as privileged.
  • Web-server and router logs showing unauthenticated POST requests to management endpoints or unusual calls to configuration functions.
  • Policy enforcement requiring authentication and network-location controls for administrative interfaces.

Automated security review tools may help identify missing authorization checks, but endpoint behavior should also be verified through authorized testing.

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 endpoint is reachable

by an untrusted network. Exploitation does not necessarily require an existing

authenticated session.

The affected function may disclose network topology and interface configuration

information, which can assist reconnaissance and targeted attacks.

Require authentication and function-level authorization before processing

requests that return network or interface configuration data, while limiting

management access to trusted networks.

Maintain an inventory of privileged endpoints, apply deny-by-default access

policies, test unauthenticated behavior, and review logs for unexpected access

to administrative functions.

Find out what's already
exploitable in your codebase.