/

CVE-2026-51708

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51708

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized configuration changes and potential wireless security degradation

Severity:

CRITICAL RISK

(9.8)

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 allows unauthenticated requests to change Wi-Fi Protected Setup (WPS) availability through the device's web interface.

An attacker who can reach the affected management endpoint may alter WPS settings without first proving authorization, potentially weakening wireless security or disrupting device configuration.

Affected context

The issue occurs in the setWiFiWpsCfg function of TOTOLINK T6 firmware 4.1.5cu.748_B20211015. It becomes risky when the device exposes the affected CGI interface to an attacker who can reach it and the endpoint processes configuration requests without adequate authentication or authorization checks.

Exploit preconditions

  • Attack surface: The TOTOLINK T6 web management CGI interface
  • Required access: Network reachability to /cgi-bin/cstecgi.cgi; valid credentials may not be required
  • Trigger point: Processing of a request handled by setWiFiWpsCfg
  • Why exploitation is possible: The function permits a configuration change without sufficiently verifying that the requester is authorized to modify WPS availability

Why this happens

The underlying bug is an authorization failure in a configuration-management endpoint. The application appears to trust requests reaching the setWiFiWpsCfg handler without consistently enforcing authentication and authorization before applying a security-sensitive setting. This behavior maps to CWE-284: Improper Access Control, in which access to a protected operation is not restricted according to the required security policy.

Potential impact

  • An unauthenticated attacker may change WPS availability
  • Wireless onboarding behavior may be altered or disrupted
  • Security controls associated with WPS could be weakened
  • Network administrators may lose expected control over device configuration
  • The device could become part of a broader attack path if the setting change supports follow-on activity

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every security-sensitive configuration handler and reducing exposure of management interfaces.

Common defensive patterns include:

  • Require authentication and authorization before changing WPS or other wireless security settings
  • Apply centralized access-control checks rather than relying only on endpoint-specific behavior
  • Bind management interfaces to trusted networks and avoid unnecessary internet exposure
  • Use secure-by-default wireless settings and minimize reliance on WPS where operationally feasible
  • Apply least privilege to administrative roles and separate read-only from configuration-changing operations
  • Record and alert on unauthenticated or unexpected configuration changes

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and review rules requiring authorization checks before configuration mutations
  • Code review signals such as CGI handlers that update device settings without an adjacent identity or role check
  • API and firmware testing that verifies unauthenticated requests cannot modify security-sensitive state
  • Web-server and device logs showing unexpected requests to configuration endpoints or changes to WPS status
  • Policy enforcement that restricts management-plane access to approved networks and administrative roles

Automated security testing and code-review tools may help identify missing authorization checks, but endpoint behavior should also be validated in a representative device environment.

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 management interface is reachable by an attacker. The practical scope depends on device exposure, network segmentation, and administrative-interface settings.

The reported issue allows an unauthenticated attacker to attempt the configuration change, provided the attacker can reach the affected CGI endpoint.

Require authentication and role-appropriate authorization before applying WPS or other security-sensitive configuration changes, while limiting management access to trusted networks.

Apply consistent authorization middleware or policy checks to all state-changing endpoints, test unauthenticated and low-privilege access paths, and monitor configuration changes for unexpected activity.

Find out what's already
exploitable in your codebase.