/

CVE-2026-51699

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51699

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Internal Host 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 router allows unauthenticated requests to reach the setDmzCfg function through the web management interface.

Under conditions where the affected endpoint is reachable, an attacker may use a crafted POST request to expose an internal host without first proving authorization.

Affected context

The issue occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015, specifically in the setDmzCfg function handled through /cgi-bin/cstecgi.cgi. Risk is higher when the router's management interface or this endpoint is reachable by untrusted users or from an exposed network boundary, and when internal host details are accepted without effective authorization checks.

Exploit preconditions

  • Attack surface: The router's HTTP management interface and the /cgi-bin/cstecgi.cgi endpoint
  • Required access: No authenticated account is required when the vulnerable request path is reachable
  • Trigger point: Processing of a crafted POST request that invokes the setDmzCfg function
  • Why exploitation is possible: The function does not adequately verify authorization before accepting a security-sensitive configuration request, allowing an unauthenticated actor to influence internal host exposure

Why this happens

The underlying bug is an authorization failure in a sensitive configuration handler. The setDmzCfg function appears to process requests that can affect DMZ or internal-host exposure without consistently enforcing an authenticated and authorized security context.

This maps to CWE-284: Improper Access Control, where access to a protected operation or resource is not sufficiently restricted. The insecure pattern is treating endpoint reachability as permission to perform a privileged network-configuration action.

Potential impact

  • An attacker may expose an internal host through the router's DMZ-related configuration
  • Internal services may become reachable from untrusted networks
  • Network segmentation controls could be weakened
  • The router's security posture may be altered without administrative approval
  • Follow-on attacks against exposed internal systems could become more likely

General mitigation guidance

Mitigation generally focuses on enforcing authorization before any security-sensitive router configuration is parsed or applied.

Common defensive patterns include:

  • Requiring authenticated, authorized administrative sessions for DMZ and host-exposure changes
  • Applying deny-by-default access controls to configuration endpoints
  • Separating public request handling from privileged configuration operations
  • Validating target hosts and network ranges against explicit policy
  • Restricting management interfaces to trusted administration networks
  • Running configuration services with the minimum privileges needed
  • Using secure-by-default network rules that do not expose internal hosts unless explicitly permitted

How teams detect issues like this

Detection approaches may include:

  • Static analysis for configuration handlers that lack authentication or authorization checks
  • Code review of CGI endpoints that modify firewall, NAT, DMZ, or routing state
  • Tests that invoke sensitive endpoints with missing, expired, or insufficient credentials
  • Web-server and router audit logs reviewed for unauthenticated POST requests to configuration paths
  • Network monitoring for unexpected changes in DMZ mappings or newly exposed internal services
  • Policy enforcement requiring security-sensitive management operations to pass centralized authorization controls

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 interface or the affected endpoint is accessible from an untrusted network. If management access is limited to a trusted administrative segment, the practical exposure is reduced.

The vulnerability description indicates that authentication is not required for the affected request path. Network reachability to the endpoint remains necessary.

Enforce authentication and fine-grained authorization before processing any DMZ or internal-host exposure request, while using deny-by-default network policies.

Treat all configuration endpoints as privileged operations, test them with unauthenticated and low-privilege requests, restrict management-plane exposure, and monitor for unauthorized network-policy changes.

Find out what's already
exploitable in your codebase.