/

CVE-2026-51625

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51625

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

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

An incorrect access control issue in the TOTOLINK T6 allows unauthenticated requests to invoke the getWiFiEasyCfg function and retrieve sensitive wireless configuration data. A remote attacker who can reach the device's CGI interface may obtain SSIDs and Wi-Fi keys by submitting a specially crafted request.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 when the /cgi-bin/cstecgi.cgi endpoint exposes the getWiFiEasyCfg function without adequately enforcing authentication or authorization. Risk is highest when the router's management interface is reachable by untrusted users or from an exposed network.

Exploit preconditions

  • Attack surface: The router's CGI management interface
  • Required access: Network reachability to the affected endpoint; authentication may not be required
  • Trigger point: Processing a request that invokes the getWiFiEasyCfg function
  • Why exploitation is possible: The function does not sufficiently verify that the requester is authorized to access wireless configuration data

Why this happens

The underlying bug is an authorization failure in a management API. Sensitive configuration data is returned based on the requested function without consistently enforcing an authentication and permission check, mapping to CWE-284: Improper Access Control. The insecure pattern is treating endpoint reachability or function selection as sufficient authorization for protected information.

Potential impact

  • An attacker may obtain configured SSIDs and Wi-Fi keys
  • Unauthorized parties could gain access to the associated wireless network
  • Exposed credentials could enable access to connected devices or internal services
  • Disclosure could support further attacks against the router or connected systems

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every management endpoint that returns sensitive configuration data.

Common defensive patterns include:

  • Require authentication and explicit authorization before invoking configuration-retrieval functions
  • Apply deny-by-default access controls to administrative CGI operations
  • Limit management interfaces to trusted networks or dedicated administration paths
  • Avoid returning plaintext secrets when they are not operationally required
  • Rotate exposed wireless credentials and review connected-device access after suspected disclosure
  • Run administrative services with only the privileges and data access they require

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static and dynamic checks for administrative endpoints lacking authentication or authorization guards
  • Code review of CGI dispatchers and functions that return credentials or network configuration
  • API inventory and policy enforcement requiring access-control checks for sensitive operations
  • Network monitoring for unauthenticated requests to management endpoints and unusual configuration-read activity
  • Automated security testing that verifies protected resources cannot be accessed through alternate function paths

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 CGI management interface is reachable by an attacker. Exploitability depends on network exposure and access-control configuration.

The described issue permits unauthenticated access to the affected function, so valid router credentials may not be required when the endpoint is reachable.

Enforce authentication and authorization before processing the function, and ensure sensitive wireless settings are not returned to callers without a verified administrative permission.

Apply deny-by-default policies to management APIs, review every sensitive endpoint for consistent access checks, restrict administrative interfaces to trusted networks, and test unauthenticated and low-privilege access paths during security assessments.

Find out what's already
exploitable in your codebase.