/

CVE-2026-51728

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51728

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Firmware Replacement and Device Compromise

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 firmware upload function allows unauthenticated attackers to submit a crafted firmware image through the device's web interface. If the upload endpoint is reachable and does not enforce authorization or adequate firmware validation, the attacker may alter the device software and compromise its operation.

Affected context

The issue occurs in the UploadFirmwareFile function of TOTOLINK T6 firmware version 4.1.5cu.748_B20211015. Risk is present where the /cgi-bin/cstecgi.cgi endpoint accepts firmware-upload requests without requiring authentication and where uploaded images are not sufficiently restricted or validated before installation.

Exploit preconditions

  • Attack surface: The router's web-management CGI endpoint
  • Required access: Network reachability to the device; authentication may not be required
  • Trigger point: A POST request that reaches the UploadFirmwareFile handler
  • Why exploitation is possible: The handler's access-control checks do not adequately restrict unauthenticated firmware-upload operations

Why this happens

The underlying bug is an authorization failure in a security-sensitive administrative operation. The firmware upload handler permits a request to reach the update workflow without first establishing that the caller has the required privileges, which maps to CWE-284: Improper Access Control. Where image authenticity, integrity, or lifecycle controls are also insufficient, an unauthorized upload may be accepted as a firmware update.

Potential impact

  • An attacker could replace device firmware with a crafted image
  • The router may be rendered unavailable or unreliable
  • Network traffic could be monitored, altered, or redirected
  • Device configuration and connected-network data may be exposed
  • The device could be incorporated into a broader attack or botnet
  • Recovery could require administrative intervention or hardware re-provisioning

General mitigation guidance

Mitigation generally focuses on protecting firmware-update workflows with defense-in-depth controls.

Common defensive patterns include:

  • Require authenticated, authorized administrative access before any firmware upload is processed
  • Enforce server-side authorization checks independently of client-side interface controls
  • Accept only firmware images with strong cryptographic signatures and trusted provenance
  • Validate image format, version, target device, integrity, and update state before installation
  • Restrict management interfaces to trusted networks and minimize their exposure
  • Run update-handling components with the least privilege needed for the operation
  • Provide safe recovery and rollback behavior when validation or installation fails

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review of CGI handlers for missing authorization gates
  • Tests that submit firmware-update requests without credentials and verify rejection
  • Review of firmware validation, signature verification, and update-state transitions
  • Web-server and device logs showing unexpected requests to firmware-upload endpoints
  • Network monitoring for externally sourced POST requests targeting management interfaces
  • Policy enforcement requiring authenticated administrative workflows for software updates

Automated security testing and code-review tools may help identify unprotected administrative actions, but device-level validation should also be tested in an isolated environment.

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 network-reachable and exposed without authentication. Exposure depends on deployment and management-interface settings.

The described flaw allows unauthenticated access to the firmware-upload operation, so a valid account may not be required when the endpoint is reachable.

Require authorization before processing uploads and enforce cryptographic firmware-signature verification, strict image validation, and device-target checks before installation.

Treat firmware updates as privileged operations, keep management interfaces isolated, test unauthenticated and low-privilege requests, and enforce secure update policies through code review and automated security testing.

Find out what's already
exploitable in your codebase.