/

CVE-2026-51618

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51618

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized 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 improper access control vulnerability in the TOTOLINK T6 allows unauthenticated attackers to retrieve setup wizard and onboarding configuration information. The issue becomes risky when the device exposes its CGI interface and fails to enforce authorization for crafted POST requests.

Affected context

The vulnerability occurs in the getWizardCfg function of TOTOLINK T6 firmware version 4.1.5cu.748_B20211015. It affects deployments where the router's /cgi-bin/cstecgi.cgi endpoint is reachable and the function returns setup or onboarding configuration data without first confirming that the requester is authorized.

Exploit preconditions

  • Attack surface: The router's HTTP CGI interface
  • Required access: Network reachability to the device; authentication may not be required
  • Trigger point: A crafted POST request processed by getWizardCfg
  • Why exploitation is possible: The function does not adequately enforce access controls before disclosing configuration information

Why this happens

The underlying flaw is an authorization failure in a sensitive configuration retrieval function. Access control checks are missing, incomplete, or applied after the disclosure decision, allowing an unauthenticated request to reach data intended for authorized setup or administrative workflows. This behavior maps to CWE-284: Improper Access Control, where protected resources are not consistently restricted according to the required security policy.

Potential impact

  • An attacker may obtain setup wizard and onboarding configuration details
  • Exposed information could assist further attacks against the router or connected services
  • Sensitive deployment or network metadata may be disclosed
  • Attackers could use the information to improve reconnaissance or targeted social engineering

General mitigation guidance

Mitigation generally focuses on enforcing authorization before processing any configuration retrieval request.

Common defensive patterns include:

  • Require authentication and explicit authorization for administrative CGI functions
  • Apply deny-by-default access policies to setup and onboarding endpoints
  • Validate session state, roles, and device ownership before returning sensitive data
  • Minimize the information returned by diagnostic and configuration APIs
  • Restrict management interfaces to trusted networks where practical
  • Run administrative services with the least privilege needed to perform their functions
  • Treat configuration and onboarding data as sensitive and reduce its exposure

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and review rules requiring authorization checks on sensitive handlers
  • Code review searches for CGI functions that return configuration data before validating sessions
  • Dynamic testing of administrative endpoints with unauthenticated and low-privilege requests
  • API inventory and policy checks ensuring setup, onboarding, and diagnostic routes are protected
  • Monitoring for unusual POST requests to CGI endpoints and repeated configuration retrievals
  • Automated security testing or code review tools that flag missing authorization enforcement

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

No authentication is expected to be required for the vulnerable request, according to the vulnerability description. Network access to the affected endpoint remains necessary.

Enforce authentication and role-based authorization before executing getWizardCfg or returning any setup-related information. Also apply deny-by-default rules to administrative endpoints.

Maintain an inventory of sensitive endpoints, require centralized authorization checks, test unauthenticated and low-privilege access paths, and monitor for unexpected configuration disclosure.

Find out what's already
exploitable in your codebase.