/

CVE-2026-51669

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51669

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized disclosure of pairing and mesh configuration

Severity:

CRITICAL RISK

(9.1)

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 critical access-control vulnerability in the TOTOLINK T6 getPairCfg function allows unauthenticated attackers to retrieve pairing and mesh-slave configuration data.

The issue becomes risky when the device exposes the affected CGI endpoint and fails to require authorization for crafted POST requests.

Affected context

The vulnerability occurs in TOTOLINK T6 devices running the affected firmware when the getPairCfg function is reachable through /cgi-bin/cstecgi.cgi. In deployments where this endpoint accepts requests without authentication or adequate authorization checks, remote unauthenticated users may be able to access configuration data associated with device pairing and mesh relationships.

Exploit preconditions

  • Attack surface: The device's HTTP CGI interface, specifically /cgi-bin/cstecgi.cgi
  • Required access: Network reachability to the management or web service; authentication may not be required
  • Trigger point: A crafted POST request invoking the getPairCfg function
  • Why exploitation is possible: The function does not consistently enforce access-control checks before returning pairing and mesh-slave configuration

Why this happens

The underlying bug is an authorization failure in which a sensitive configuration retrieval function trusts the request context without verifying that the caller is permitted to access the data. This maps to CWE-284: Improper Access Control, because the application exposes protected information through an interface that does not adequately enforce authentication and authorization boundaries.

Potential impact

  • Attackers may obtain pairing configuration data
  • Attackers could disclose mesh-slave relationships and device topology
  • Exposed configuration may support follow-on targeting of connected devices
  • Network privacy and administrative control may be weakened
  • Sensitive values could be reused in broader device compromise attempts

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every sensitive CGI operation and reducing the amount of configuration returned to untrusted callers.

Common defensive patterns include:

  • Require authentication and explicit authorization before processing configuration-retrieval functions
  • Apply deny-by-default access policies to management endpoints
  • Return only the minimum configuration data required for an authorized operation
  • Separate pairing and mesh-management privileges from general device access
  • Restrict management interfaces to trusted network segments where practical
  • Avoid exposing administrative CGI services directly to untrusted networks
  • Log and rate-limit unauthorized access attempts without disclosing sensitive response details

How teams detect issues like this

Organizations can identify similar weaknesses through:

  • Static analysis and endpoint audits for sensitive handlers that lack authentication or authorization checks
  • Code review signals such as configuration retrieval occurring before identity and privilege verification
  • Dynamic testing of management endpoints with anonymous requests and invalid session contexts
  • API inventories that classify pairing, topology, and credential-related responses as protected data
  • Policy enforcement requiring authorization middleware for all administrative CGI operations
  • Monitoring for unusual POST requests to CGI endpoints and repeated configuration retrieval attempts

Automated application-security testing and code-review tools may help identify publicly reachable handlers that return sensitive data without an established 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 remotely exploitable when the affected CGI endpoint is network-reachable and the device does not restrict management access to trusted networks.

The reported issue permits unauthenticated access, although network reachability and exposure of the web interface remain necessary conditions.

Enforce authentication and authorization before invoking configuration retrieval, use deny-by-default endpoint policies, and return only the minimum data needed by authorized users.

Maintain an inventory of sensitive endpoints, require centralized authorization checks, test anonymous and low-privilege request paths, and monitor access to administrative configuration APIs.

Find out what's already
exploitable in your codebase.