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

New CVE Detected

CVE-2026-51708 – Unauthenticated WPS Configuration Tampering – TOTOLINK T6 Router Firmware 4.1.5cu.7

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

Summary

CVE-2026-51708 is an incorrect access control vulnerability (CWE-284) in the setWiFiWpsCfg function of the TOTOLINK T6 web management interface, firmware version 4.1.5cu.748_B20211015. The flaw allows a remote, unauthenticated attacker to change the device’s WPS (Wi-Fi Protected Setup) availability by sending a crafted POST request to /cgi-bin/cstecgi.cgi. It carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The setWiFiWpsCfg function in /cgi-bin/cstecgi.cgi fails to enforce authentication or authorization checks before processing requests that alter WPS settings.
  • Trigger conditions: An attacker sends an HTTP POST request to /cgi-bin/cstecgi.cgi with topicurl=setWiFiWpsCfg and associated WPS parameters, with no valid session or credentials required.
  • Attack vector: Network-based, requiring no authentication and no user interaction (AV:N/AC:L/PR:N/UI:N).
  • Impact: Successful exploitation lets an unauthenticated attacker change WPS availability on the device, which can weaken wireless security controls and expose the network to further attack. CISA’s SSVC assessment rates the attack as automatable with total technical impact.

Affected software

  • TOTOLINK T6, firmware version 4.1.5cu.748_B20211015

Severity

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

Mitigation and recommended actions

  • Immediate: No confirmed patched firmware version has been published by TOTOLINK for this vulnerability at the time of writing; check the TOTOLINK support/download portal for the T6 model regularly for an updated firmware release addressing this issue.
  • If no patch is available:
    • Restrict access to the router’s web management interface (/cgi-bin/cstecgi.cgi) to trusted internal networks only; do not expose it to the internet.
    • Disable remote/WAN-side administration on the device if enabled.
    • Place management interfaces behind a VPN or firewall rule limiting access to known administrator IP addresses.
    • Monitor for unexpected changes to WPS settings and disable WPS entirely if not required.

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