Summary
A broken access control vulnerability in the TOTOLINK T6 WPS configuration endpoint allows unauthenticated requests to retrieve sensitive WPS settings, including the current PIN. An attacker who can reach the device's management interface may disclose this information by sending a specially crafted POST request.
Affected context
The issue occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 firmware, specifically in the getWiFiWpsCfg function exposed through /cgi-bin/cstecgi.cgi. Risk is present when the endpoint is reachable and fails to require authentication before returning WPS configuration data.
Exploit preconditions
- Attack surface: The device's HTTP management interface and
/cgi-bin/cstecgi.cgiendpoint - Required access: Network connectivity to the affected endpoint; authentication may not be required
- Trigger point: A crafted POST request invoking the WPS configuration retrieval function
- Why exploitation is possible: Access control checks do not adequately restrict retrieval of configuration containing the current WPS PIN
Why this happens
The underlying bug is an authorization failure in which a sensitive configuration retrieval function does not consistently enforce authentication or authorization before returning data. This maps to CWE-284: Improper Access Control, because the endpoint permits an untrusted requester to access information intended for authorized administrators.
Potential impact
- An attacker may obtain the current WPS PIN
- Unauthorized users could gain access to the wireless network through exposed WPS credentials
- Attackers could use the disclosed configuration to weaken or bypass wireless access controls
- Network confidentiality and device integrity could be reduced
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every sensitive endpoint and minimizing the information returned to unauthenticated clients.
Common defensive patterns include:
- Require authentication and appropriate administrative authorization before exposing WPS configuration
- Apply consistent server-side access control rather than relying on client-side restrictions
- Return only the minimum data required for an authorized operation
- Disable WPS when it is not needed and prefer stronger wireless authentication controls
- Isolate device management interfaces from untrusted networks and apply least-privilege administrative access
How teams detect issues like this
Organizations can detect similar issues through:
- Static and dynamic analysis of management endpoints for missing authorization checks
- Code review of handlers that return credentials, PINs, or security configuration
- API tests that verify unauthenticated and low-privilege requests receive denial responses
- Network monitoring for unusual POST requests to configuration endpoints
- Policy enforcement requiring authentication coverage for all sensitive administrative functions

