/

CVE-2026-51647

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51647

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

An incorrect access-control check in the TOTOLINK T6 router's getCrpcCfg function may allow unauthenticated attackers to retrieve cloud remote-control status and URL information. The issue becomes risky when the vulnerable CGI endpoint is reachable and accepts crafted POST requests without requiring effective authentication.

Affected context

The vulnerability affects TOTOLINK T6 devices using the affected firmware release, where the getCrpcCfg function is exposed through the /cgi-bin/cstecgi.cgi endpoint. Risk depends on whether the endpoint is reachable by an attacker and whether access-control enforcement is absent or improperly applied to the relevant request.

Exploit preconditions

  • Attack surface: The router's HTTP CGI interface, specifically /cgi-bin/cstecgi.cgi
  • Required access: No valid authentication is expected to be required
  • Trigger point: A crafted POST request that invokes the getCrpcCfg function
  • Why exploitation is possible: The function does not consistently enforce authorization before returning cloud remote-control status and URL information

Why this happens

The underlying bug is an authorization failure in which a sensitive configuration-status operation can be reached without an effective access check. This maps to CWE-284, Improper Access Control, because the application fails to reliably restrict access to protected functionality and information based on the requester's identity or privileges.

Potential impact

  • An unauthenticated attacker may obtain cloud remote-control status
  • An attacker could learn remote-control URL information
  • Disclosed information could support device profiling or follow-on attacks
  • Exposure of management-related details may weaken the router's security boundary

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently at the

server-side function boundary rather than relying on client behavior or

request formatting.

Common defensive patterns include:

  • Require authenticated, authorized sessions for sensitive CGI operations
  • Apply deny-by-default access policies to management and cloud-control functions
  • Validate authorization before processing or returning protected data
  • Minimize the information returned by status and configuration endpoints
  • Run administrative services with the least privileges necessary
  • Reduce exposure of router management interfaces to untrusted networks

How teams detect issues like this

Detection approaches may include:

  • Static analysis for CGI handlers that return sensitive data without an authorization check
  • Code review of function dispatch, session validation, and privilege enforcement paths
  • Tests that exercise administrative endpoints with missing, expired, and low-privilege sessions
  • Web-server policy monitoring for unauthenticated requests to management CGI functions
  • Network and device logs reviewed for unusual POST activity involving /cgi-bin/cstecgi.cgi

Automated security testing and policy-as-code checks can help identify authorization

gaps before deployment.

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 and the affected function can be invoked without authentication.

Exposure depends on network placement and management-interface configuration.

The described issue allows unauthenticated access, so a valid account may not

be required when the vulnerable endpoint is accessible.

Enforce authentication and authorization at the getCrpcCfg function boundary,

use deny-by-default rules for sensitive CGI operations, and return only the

minimum necessary information.

Perform authorization checks on every protected server-side operation, include

unauthenticated and low-privilege endpoint tests in security testing, and

restrict management interfaces to trusted networks.

Find out what's already
exploitable in your codebase.