/

CVE-2026-51696

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51696

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Network Exposure

Severity:

CRITICAL RISK

(9.8)

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 allows requests to the setPortForwardRules function without proper authentication or authorization. An unauthenticated attacker who can reach the router's management endpoint may submit a crafted POST request to expose internal services through unauthorized port-forwarding rules.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 when the router processes requests to /cgi-bin/cstecgi.cgi that invoke the setPortForwardRules function. Risk is present where the management interface is reachable by an unauthenticated party and the function does not consistently enforce access-control checks before changing port-forwarding configuration.

Exploit preconditions

  • Attack surface: The router's web management endpoint at /cgi-bin/cstecgi.cgi
  • Required access: Network reachability to the endpoint; valid authentication may not be required
  • Trigger point: Processing of a crafted POST request targeting setPortForwardRules
  • Why exploitation is possible: The function permits configuration changes without adequately verifying the requester's authorization

Why this happens

The underlying issue is an authorization failure in a security-sensitive configuration handler. The setPortForwardRules function can process port-forwarding changes without enforcing the access decision required to distinguish trusted administrative requests from unauthenticated input. This maps to CWE-284: Improper Access Control, in which a resource or operation is not adequately restricted to authorized users or contexts.

Potential impact

  • Internal services may become reachable from external networks
  • Attackers could bypass intended network segmentation
  • Administrative interfaces or other sensitive services could be exposed
  • Unauthorized port-forwarding changes could support follow-on attacks
  • Router and connected-network confidentiality or integrity could be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every security-sensitive configuration operation.

Common defensive patterns include:

  • Require authenticated, authorized administrative sessions before processing port-forwarding changes
  • Apply centralized access-control checks at the endpoint and function levels
  • Reject requests when authentication state, session scope, or privilege cannot be verified
  • Validate port-forwarding targets and restrict exposure to approved interfaces and services
  • Use least-privilege administrative roles and separate read-only from configuration permissions
  • Record and monitor changes to forwarding rules, with secure defaults that minimize external exposure

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis of CGI handlers and configuration APIs for missing authentication or authorization checks
  • Code review signals such as direct state changes from request parameters without centralized policy enforcement
  • Dynamic tests that submit configuration requests with absent, expired, or insufficient credentials
  • Monitoring for unexpected changes to port-forwarding rules and newly exposed services
  • Policy enforcement requiring authorization tests for every administrative configuration endpoint
  • Automated security review tools that identify unauthenticated access to sensitive 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

It may be remotely exploitable when the affected management endpoint is reachable by an attacker. Exploitability depends on network exposure and device administration settings.

The described flaw allows unauthenticated attackers to invoke the affected operation, so valid administrative credentials may not be required when the endpoint is reachable.

Enforce authentication and authorization before any port-forwarding rule is created, modified, or deleted, and apply secure defaults that prevent unintended external exposure.

Treat all configuration-changing endpoints as privileged operations, centralize authorization checks, test unauthenticated and low-privilege requests, and monitor sensitive network-configuration changes.

Find out what's already
exploitable in your codebase.