/

CVE-2026-51644

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51644

Deferred

Vulnerability type

Category:

Broken 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

TOTOLINK T6 contains an access-control weakness in the getCrpcConfig function that handles cloud remote-control configuration requests. An unauthenticated attacker may obtain cloud remote-control status and URL information by sending a specially crafted POST request to the affected CGI endpoint.

Affected context

The issue occurs in TOTOLINK T6 devices running the affected firmware when the cloud remote-control configuration function is reachable through the web-management CGI interface. Risk is higher when the device exposes /cgi-bin/cstecgi.cgi to untrusted networks and the relevant request is processed without effective authentication or authorization checks.

Exploit preconditions

  • Attack surface: The device's HTTP/HTTPS management interface and CGI request handler
  • Required access: Network connectivity to the exposed management endpoint; valid credentials may not be required
  • Trigger point: A crafted POST request directed to /cgi-bin/cstecgi.cgi that invokes getCrpcConfig
  • Why exploitation is possible: The function does not adequately verify whether the requester is authorized to retrieve cloud remote-control configuration data

Why this happens

The vulnerability results from an incomplete access-control check in a function that returns sensitive device configuration information. The request handler permits access to cloud remote-control status and URL data without consistently binding the operation to an authenticated and authorized session. This behavior maps to CWE-284: Improper Access Control, in which a protected resource or operation lacks an effective authorization decision.

Potential impact

  • An attacker may obtain cloud remote-control status information
  • An attacker could learn cloud service URL details associated with the device
  • Disclosed information may support targeted attacks against device-management or cloud-control infrastructure
  • Exposure of management metadata can increase the impact of related device vulnerabilities

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side function and endpoint boundaries rather than relying on request format or client behavior.

Common defensive patterns include:

  • Requiring authenticated, valid, and appropriately privileged sessions before returning cloud-control data
  • Applying deny-by-default authorization to CGI actions and configuration-read operations
  • Limiting management interfaces to trusted networks or administrative channels
  • Returning only the minimum information needed for the requesting workflow
  • Avoiding disclosure of sensitive service endpoints to unauthenticated clients
  • Reviewing session validation, authorization, and error-handling logic consistently across related handlers

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review checks for CGI handlers that access configuration without nearby authorization enforcement
  • Tests that invoke configuration-read actions with no session, expired sessions, and insufficient privileges
  • Dynamic monitoring for unauthenticated POST requests to management CGI endpoints
  • API and endpoint inventories that identify administrative operations exposed beyond trusted network boundaries
  • Policy enforcement requiring authentication and authorization tests for every management operation

Automated security testing and code-review tools may help identify missing authorization checks, but endpoint-specific verification remains important.

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 device management interface is reachable by an attacker and the affected CGI request is accepted without authentication.

The described behavior indicates that valid credentials may not be required. Network access to the exposed endpoint is the primary prerequisite.

Enforce authentication and authorization inside getCrpcConfig and at the endpoint boundary, then return only the minimum necessary configuration data.

Apply deny-by-default access policies, test management endpoints with unauthenticated and low-privilege sessions, and restrict administrative interfaces to trusted networks.

Find out what's already
exploitable in your codebase.