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

New CVE Detected

CVE-2026-51690 – Unauthenticated WAN Configuration Tampering – TOTOLINK T6 4.1.5cu.748_B20211015

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

Summary

CVE-2026-51690 is an improper access control vulnerability in the setWanCfg function of TOTOLINK T6 routers running firmware 4.1.5cu.748_B20211015. It allows an unauthenticated, remote attacker to send a crafted POST request to the device’s CGI handler and alter the router’s upstream (WAN) provisioning and connectivity settings. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The setWanCfg function, exposed through the /cgi-bin/cstecgi.cgi binary, does not enforce authentication or session validation before processing WAN configuration change requests.
  • Trigger conditions: An attacker sends a specially crafted HTTP POST request targeting the setWanCfg action on /cgi-bin/cstecgi.cgi, with no prior login or valid session required.
  • Attack vector: Network — the vulnerable CGI endpoint is reachable over the router’s exposed HTTP management interface without authentication.
  • Impact: Unauthenticated modification of upstream provisioning and connectivity settings, which can be used to disrupt internet connectivity, redirect traffic, or otherwise manipulate WAN-side network behavior. The published CVSS vector indicates high confidentiality and integrity impact with no availability impact.

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

  • No vendor patch has currently been identified for this specific firmware version; consult TOTOLINK’s official support/download channels for updated firmware for the T6 model and apply it as soon as it becomes available.
  • Until a patch is released, restrict access to the router’s management/CGI interface (/cgi-bin/cstecgi.cgi) — disable remote/WAN-side management, disable UPnP, and limit administrative access to trusted internal networks only.
  • Place affected devices behind a firewall or VPN so the management interface is not directly reachable from the internet.
  • Monitor for unexpected changes to WAN/provisioning settings and consider replacing or isolating end-of-life TOTOLINK devices that no longer receive security updates.

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
  • Page title: 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