/

CVE-2026-51721

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51721

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Mesh Configuration Modification

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 4.1.5cu.748_B20211015 firmware allows unauthenticated attackers to change the mesh pairing state. The issue is triggered through a crafted POST request to the device's CGI interface and may enable unauthorized network configuration changes.

Affected context

The vulnerability occurs in the setPairCfg function exposed through /cgi-bin/cstecgi.cgi on affected TOTOLINK T6 devices. Risk exists when the endpoint accepts pairing-state changes without adequately verifying the caller's identity, authorization, or administrative privileges.

Exploit preconditions

  • Attack surface: HTTP CGI endpoint exposed by the router
  • Required access: Network reachability to the device; authentication may not be required
  • Trigger point: A crafted POST request handled by setPairCfg
  • Why exploitation is possible: The function permits a security-sensitive mesh pairing change without sufficient access-control enforcement

Why this happens

The underlying bug is an authorization failure in a state-changing administrative function. The endpoint appears to rely on insufficient or missing authentication and authorization checks before applying mesh pairing configuration changes. This behavior maps to CWE-284: Improper Access Control, where a protected resource or operation is not adequately restricted to authorized users.

Potential impact

  • An attacker may alter the device's mesh pairing state
  • Unauthorized devices could potentially be added to or removed from the mesh relationship
  • Network availability or connectivity could be disrupted
  • An attacker could weaken network trust relationships or facilitate further unauthorized access
  • Security monitoring and administrative expectations could be undermined

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every state-changing administrative endpoint.

Common defensive patterns include:

  • Requiring authentication and explicit administrative authorization before changing mesh configuration
  • Applying consistent access-control middleware to all CGI handlers
  • Rejecting requests that lack valid sessions, anti-forgery protections, or required privileges
  • Limiting management interfaces to trusted networks and disabling unnecessary external exposure
  • Validating requested pairing changes against an approved device and configuration policy
  • Running management services with only the privileges needed to perform their functions

How teams detect issues like this

Organizations can look for improper access control through:

  • Static analysis rules identifying state-changing handlers without nearby authentication and authorization checks
  • Code review of CGI endpoints that modify pairing, routing, or other security-sensitive state
  • Tests that invoke administrative operations with no credentials, expired sessions, and insufficient roles
  • Web-server and device logs showing unauthenticated POST requests to configuration endpoints
  • Policy enforcement requiring authorization middleware and negative access-control tests for all management APIs
  • Automated security review tools that flag externally reachable state-changing functions

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 endpoint is reachable. Exposure depends on device network placement and management-interface configuration.

The described issue allows unauthenticated attackers to submit the relevant request, so valid credentials may not be required when the endpoint is accessible.

Enforce authentication and authorization before processing any mesh pairing changes, and apply the same controls consistently across all administrative endpoints.

Use centralized authorization middleware, perform negative access-control testing, restrict management interfaces to trusted networks, and monitor unauthenticated requests to state-changing endpoints.

Find out what's already
exploitable in your codebase.