/

CVE-2026-51650

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51650

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 incorrect access-control check in the TOTOLINK T6 getRemoteCfg function may expose remote-management status and port information through the device's CGI interface.

Because the affected endpoint may accept crafted requests without authentication, an unauthenticated attacker could retrieve configuration details that help assess or target the device.

Affected context

This vulnerability affects TOTOLINK T6 devices running firmware 4.1.5cu.748_B20211015 when the getRemoteCfg function is reachable through /cgi-bin/cstecgi.cgi and does not adequately enforce authentication or authorization before returning remote-management information. Exposure depends on network reachability of the device's management interface and its deployment configuration.

Exploit preconditions

  • Attack surface: The device's CGI management endpoint at /cgi-bin/cstecgi.cgi
  • Required access: Network connectivity to the endpoint; authentication may not be required
  • Trigger point: A crafted POST request processed by the getRemoteCfg function
  • Why exploitation is possible: The function may disclose remote-management enablement and port information without verifying that the requester is authorized to access it

Why this happens

The underlying bug is an authorization failure in a management API. The getRemoteCfg function appears to expose sensitive configuration metadata without consistently enforcing an authentication and authorization decision before processing the request and returning data. This maps to CWE-284: Improper Access Control, where access to a protected resource or operation is not sufficiently restricted.

Potential impact

  • An attacker may learn whether remote management is enabled
  • An attacker may obtain the port used for remote management
  • The disclosed information could support reconnaissance and targeted follow-on attacks
  • Network administrators may lose confidentiality over device-management configuration

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every management API entry point and minimizing information returned to unauthenticated callers.

Common defensive patterns include:

  • Requiring authentication and explicit authorization before serving remote-management configuration
  • Applying deny-by-default controls to CGI and administrative endpoints
  • Returning only the minimum information necessary for an authorized operation
  • Reducing exposure of device-management interfaces to untrusted networks
  • Separating administrative functions from publicly reachable request paths
  • Running management services with least privilege and restrictive network policies

How teams detect issues like this

Detection approaches may include:

  • Static analysis for management handlers that return configuration data without an authorization check
  • Code review of CGI dispatch logic, especially functions that process POST parameters
  • Testing unauthenticated and low-privilege requests against administrative endpoints
  • Monitoring logs for repeated requests to configuration-disclosure functions
  • Policy enforcement requiring authentication and authorization middleware for all management APIs
  • Automated security testing or neutral code-review tools that identify missing access-control checks

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's CGI management endpoint is reachable by an attacker and the endpoint accepts requests without authentication.

The primary requirement is network access to /cgi-bin/cstecgi.cgi; the vulnerable behavior is described as unauthenticated, so valid device credentials may not be necessary.

Enforce authentication and authorization before getRemoteCfg processes requests or returns remote-management details, while limiting responses to the minimum required data.

Apply centralized access-control checks to all administrative endpoints, use deny-by-default policies, restrict management interfaces at the network boundary, and include unauthorized-request tests in security reviews.

Find out what's already
exploitable in your codebase.