/

CVE-2026-51661

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51661

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized disclosure of network and port-forwarding configuration

Severity:

CRITICAL RISK

(9.1)

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

A critical access-control vulnerability in the TOTOLINK T6 router allows unauthenticated users to retrieve port-forwarding rules through the getPortForwardRules function.

An attacker who can reach the router's management endpoint may send a specially crafted POST request and disclose forwarding configuration without first authenticating.

Affected context

The issue occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015 when the web management interface exposes the getPortForwardRules function through /cgi-bin/cstecgi.cgi. Risk depends on whether the endpoint is reachable by an untrusted network and whether the function fails to enforce authentication and authorization before returning configuration data.

Exploit preconditions

  • Attack surface: The router's HTTP management endpoint at /cgi-bin/cstecgi.cgi
  • Required access: Network connectivity to the exposed management interface; valid credentials may not be required
  • Trigger point: A crafted POST request invoking the getPortForwardRules function
  • Why exploitation is possible: The function does not adequately verify authentication or authorization before disclosing port-forwarding rules

Why this happens

The vulnerability results from an incorrect access-control decision in a sensitive management function. The application appears to process a request for port-forwarding configuration without reliably establishing that the requester is authorized to view it.

This maps to CWE-284: Improper Access Control, where access restrictions are missing, incomplete, or applied inconsistently to a protected resource.

Potential impact

  • An unauthenticated attacker may obtain port-forwarding rules
  • Disclosed rules could reveal internal hosts, services, and externally reachable ports
  • Attackers could use the information to improve reconnaissance against devices on the local network
  • The exposure may increase the risk of follow-on attacks against forwarded services
  • Network configuration details could be used to support targeted intrusion attempts

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization consistently across every router management operation.

Common defensive patterns include:

  • Requiring an authenticated session before processing configuration-disclosure requests
  • Applying explicit authorization checks to each sensitive function rather than relying only on endpoint-level assumptions
  • Limiting management interfaces to trusted administration networks
  • Disabling remote management exposure where it is not required
  • Returning only the minimum configuration data necessary for an authorized operation
  • Running management services with narrowly scoped privileges and defensive request validation
  • Monitoring and protecting administrative interfaces with network access controls

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and review of CGI handlers for missing authentication or authorization checks
  • Code-review signals where sensitive functions return configuration data before identity and permission validation
  • Dynamic testing of management endpoints with unauthenticated and low-privilege sessions
  • API and policy tests that verify every configuration-read operation has an explicit authorization decision
  • Network monitoring for unusual POST requests to router management endpoints
  • Automated security review tools configured to flag inconsistent access-control 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 management endpoint is reachable from an untrusted network. Exposure is more limited when administration is restricted to a trusted local network.

Based on the description, authentication may not be required. Network access to the affected CGI endpoint is the primary prerequisite.

Enforce authentication and per-function authorization before returning port-forwarding rules or any other sensitive management data.

Use centralized access-control checks, test endpoints with unauthenticated and low-privilege requests, minimize management-plane exposure, and continuously review configuration-disclosure functions.

Find out what's already
exploitable in your codebase.