/

CVE-2026-51617

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51617

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Sensitive 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

TOTOLINK T6 4.1.5cu.748_B20211015 contains an access-control weakness in the getSysStatusCfg function that may expose sensitive system and network information to unauthenticated callers. The issue becomes risky when the affected CGI endpoint is reachable and does not require authentication before returning router status data.

Affected context

The vulnerability occurs in the TOTOLINK T6 web-management interface, specifically the getSysStatusCfg functionality served through /cgi-bin/cstecgi.cgi. Deployments may be exposed when this endpoint is network-reachable and access controls do not distinguish authenticated administrative requests from unauthenticated requests. The returned data can include operational details, firmware information, device identifiers, network addresses, wireless settings, and connected-client statistics.

Exploit preconditions

  • Attack surface: The router's HTTP management CGI interface
  • Required access: Network reachability to the affected endpoint; valid credentials may not be required
  • Trigger point: A POST request processed by the getSysStatusCfg function
  • Why exploitation is possible: The function may return administrative status information without first enforcing appropriate authentication and authorization

Why this happens

The underlying bug is an authorization failure in which a sensitive status operation does not consistently enforce access-control checks before processing a request and returning protected information. This behavior maps to CWE-284, Improper Access Control, because the application fails to restrict access to resources according to the caller's identity and privileges. The insecure pattern is exposing administrative diagnostics through an endpoint whose authorization boundary is missing, incomplete, or applied after sensitive data has already been selected.

Potential impact

  • An attacker may learn the router's firmware version and operating mode.
  • An attacker could obtain serial numbers and WAN/LAN addressing information.
  • Wireless SSIDs and encryption keys may be disclosed.
  • Connected-client statistics could be used for device and network

reconnaissance.

  • Exposed information may support follow-on attacks against the router,

connected devices, or wireless network.

General mitigation guidance

Mitigation generally focuses on enforcing authorization before any sensitive

status data is accessed or returned.

Common defensive patterns include:

  • Require authenticated, appropriately privileged sessions for administrative

status operations.

  • Apply deny-by-default access control to CGI endpoints and management APIs.
  • Return only the minimum status fields needed for the requesting role.
  • Avoid exposing wireless keys, device identifiers, and internal addresses

through broadly accessible status responses.

  • Restrict management interfaces to trusted administration networks rather

than general or internet-facing access.

  • Use secure session validation, consistent authorization middleware, and

centralized policy enforcement for all management functions.

  • Treat endpoint reachability and authentication state as untrusted until

explicitly verified.

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and endpoint reviews that locate sensitive handlers without

preceding authentication and authorization checks.

  • Code-review searches for CGI functions returning configuration or status

objects directly from unauthenticated request paths.

  • Dynamic tests that compare responses for unauthenticated, low-privilege, and

administrative sessions.

  • API and web-management policies requiring explicit authorization for

configuration, credential, identifier, and network-topology data.

  • Monitoring for unexpected requests to management CGI endpoints and responses

containing firmware, credential, or client-information fields.

Automated application-security testing can help detect authorization

inconsistencies across equivalent management operations.

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

Exploitability depends on network reachability. A caller who can access the

router's affected management interface may be able to request the exposed

status information without being authenticated.

The primary requirement is connectivity to the relevant CGI endpoint. Valid

administrative credentials may not be necessary when the endpoint fails to

enforce authentication.

Enforce authentication and role-based authorization before processing the

status request, and return only data necessary for the caller's privilege

level.

Use centralized access-control middleware, deny-by-default management APIs,

least-privilege response design, and automated tests covering unauthenticated

and lower-privilege requests.

Find out what's already
exploitable in your codebase.