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

Back
New CVE Detected

CVE-2026-51696 – Unauthenticated Port-Forward Rule Exposure – TOTOLINK T6 4.1.5cu.748_B20211015

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-51696 is an incorrect access control vulnerability (CWE-284) in the setPortForwardRules function of the TOTOLINK T6 router running firmware 4.1.5cu.748_B20211015. The flaw allows an unauthenticated remote attacker to send a crafted HTTP POST request to the device’s management CGI endpoint and modify port-forwarding rules, exposing internal services to the internet. The issue carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: the setPortForwardRules handler in /cgi-bin/cstecgi.cgi does not enforce authentication or session validation before processing configuration changes.
  • Trigger condition: an attacker sends a POST request containing {"topicurl":"setPortForwardRules"} along with port-forwarding parameters (e.g., internal IP, internal port, external port) directly to the CGI endpoint.
  • Attack vector: network-based, requires no credentials and no user interaction.
  • Impact: attacker-controlled port-forwarding rules can route external traffic to internal network services, exposing devices and services behind the router that were not intended to be internet-facing.

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 fixed firmware version has been published by TOTOLINK for this issue at this time; check the vendor’s download page regularly for an updated firmware release for the T6 model and apply it as soon as it becomes available.
  • If no patch: restrict access to the router’s web management interface so it is not reachable from the internet (disable remote/WAN management), place the device behind a firewall or VPN, and review existing port-forwarding rules for unauthorized entries. Consider replacing or isolating the device on a segmented network until a fix is released.

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, N600R (Firmware version V...), TOTOLINK

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge