Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-51729 – Unauthenticated Device Deletion / Access Control Bypass – TOTOLINK T6 4.1.5cu.748_B

Be the first to know when new zero-days emerge:

Summary

CVE-2026-51729 is an incorrect access control vulnerability in the delDevice function of the TOTOLINK T6 router firmware (version 4.1.5cu.748_B20211015). The flaw allows an unauthenticated, remote attacker to send a crafted HTTP POST request to the device’s CGI web management interface and delete a managed "slave" device entry without any authentication. It carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The delDevice function, reachable through the router’s web management CGI handler, fails to verify that the requester is an authenticated/authorized session before processing a device-deletion request (CWE-284: Improper Access Control).
  • Trigger conditions: An attacker sends a crafted POST request to /cgi-bin/cstecgi.cgi invoking the delDevice action; no valid session token or credentials are required.
  • Attack vector: Network-based, exploitable remotely against the device’s exposed web management interface (AV:N, AC:L, PR:N, UI:N).
  • Impact: Unauthenticated removal of a managed slave device from the router’s configuration, resulting in a loss of integrity/availability of the device management state (per the CVSS vector, high confidentiality and integrity impact, no availability impact recorded).

Affected software

  • TOTOLINK T6, firmware version 4.1.5cu.748_B20211015

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: No vendor patch has been published for this CVE as of research time. Check TOTOLINK’s official download page for a firmware update addressing this issue and apply it as soon as it becomes available.
  • If no patch is available: Restrict or disable remote/internet access to the router’s web management interface (/cgi-bin/cstecgi.cgi); only allow management from trusted internal networks. Place the device behind a firewall or VPN, disable WAN-side administration, and monitor for unexpected POST requests to the CGI endpoint.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /cgi-bin/cstecgi.cgi, TOTOLINK

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge