/

CVE-2026-51619

Severity:

HIGH RISK

(7.5)

Improper Access Control (CWE-284) in TOTOLINK T6 API

CVE-2026-51619

Deferred

Vulnerability type

Category:

Improper 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

An improper access control vulnerability in the TOTOLINK T6 router allows unauthenticated attackers to retrieve online client information through the device's CGI interface. The issue becomes risky when the affected endpoint exposes client-status data without verifying the requester's authorization.

Affected context

The vulnerability occurs in the getOnlineClient function of TOTOLINK T6 firmware 4.1.5cu.748_B20211015. It affects deployments where the /cgi-bin/cstecgi.cgi endpoint processes client-information requests without requiring authentication or enforcing an appropriate authorization check.

Exploit preconditions

  • Attack surface: The router's HTTP or CGI management interface
  • Required access: Network reachability to the affected endpoint; authentication may not be required
  • Trigger point: A crafted POST request processed by the getOnlineClient function
  • Why exploitation is possible: The endpoint does not adequately verify whether the requester is authorized to access online client information

Why this happens

The underlying issue is an authorization failure in an endpoint that returns client-status information without consistently enforcing an access-control decision. This maps to CWE-284: Improper Access Control, where a system fails to restrict access to a protected resource or operation according to the intended security policy.

Potential impact

  • An unauthenticated party may obtain information about devices connected to the router
  • Exposed client details could support network reconnaissance
  • Attackers could use the information to identify targets for follow-on attacks
  • Disclosure may increase privacy and operational risks for the local network

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every endpoint that exposes device or network information.

Common defensive patterns include:

  • Requiring authentication before processing client-information requests
  • Applying explicit authorization checks based on the requesting principal and resource
  • Returning only the minimum client data required by an authorized operation
  • Disabling unnecessary administrative interfaces and restricting management access to trusted networks
  • Using secure-by-default management settings and isolating router administration from untrusted network segments
  • Applying least privilege to management functions and service accounts

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for sensitive handlers without nearby authentication and authorization enforcement
  • Review of CGI routing logic, especially functions that return network-topology or connected-device information
  • Dynamic testing that compares endpoint behavior for authenticated and unauthenticated requests
  • Web-application firewall or router-management policies that restrict access to administrative CGI paths
  • Logging and alerting for repeated unauthenticated POST requests to management endpoints

Automated security testing tools may help identify endpoints that disclose protected information without an authorization decision.

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 by an attacker who can reach the router's affected CGI interface. The practical scope depends on management-interface exposure and network segmentation.

The reported issue allows unauthenticated access to online client information, so valid credentials may not be required when the endpoint is reachable.

Require authentication and enforce an explicit authorization check before returning client information. The endpoint should also disclose only necessary data.

Apply centralized access-control middleware, test sensitive endpoints without credentials, restrict administrative interfaces to trusted networks, and review all information-returning handlers for consistent authorization enforcement.

Find out what's already
exploitable in your codebase.