Security readout for executives and security teams
Plain-English summary
A TOTOLINK T6 router running firmware 4.1.5cu.748_B20211015 may let an unauthenticated network attacker change its operating mode. Because this could alter traffic handling and expose or redirect communications, affected devices warrant urgent review, especially where their management interface is reachable from untrusted networks.
Executive priority
Treat confirmed devices as an urgent remediation item. Prioritize externally or broadly reachable management interfaces first, restrict access immediately, and seek vendor guidance. The critical score and unauthenticated network path justify rapid action, although the sources do not establish active exploitation or identify a confirmed patched release.
Technical view
CVE-2026-51717 is an incorrect access-control flaw (CWE-284) in setOpModeCfg. A crafted POST request to /cgi-bin/cstecgi.cgi can change operating mode without authentication. CVSS 3.1 rates it 9.1: network-accessible, low complexity, no privileges or user interaction, with high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Exposure is limited by the supplied evidence to TOTOLINK T6 devices running firmware 4.1.5cu.748_B20211015. Risk is greatest when the management endpoint is reachable from the internet, guest networks, or other untrusted segments. The bundle provides no CPEs or broader affected-version range, so do not assume other models or releases are affected.
Exploitation context
The vulnerability reportedly requires no authentication, privileges, or user interaction and has low attack complexity. However, the supplied bundle says it is not in KEV and provides no evidence of active exploitation, public campaigns, or confirmed weaponization. Public researcher coordination references exist, but exploitation prevalence remains unknown.
Researcher notes
The CVE description identifies one exact model, firmware build, function, and endpoint, while structured affected-product metadata is listed as n/a. That inconsistency and the absence of CPEs constrain automated matching. The sources do not establish whether default configuration is vulnerable, whether adjacent versions are affected, or which release fixes the issue.
Mitigation direction
- Identify TOTOLINK T6 devices and isolate those running firmware 4.1.5cu.748_B20211015.
- Restrict router administration to trusted management networks and prevent internet or guest-network access.
- Check official TOTOLINK guidance for an updated firmware or vendor-approved mitigation; the bundle confirms no fix.
- Monitor for unexpected operating-mode or network-routing changes until remediation is confirmed.
Validation and detection
- Inventory device model and firmware version through approved administrative or asset-management channels.
- Verify the management interface is unreachable from internet, guest, and other untrusted networks.
- Review available configuration history and logs for unexplained operating-mode changes.
- After remediation, confirm access restrictions remain effective and the operating mode matches the approved configuration.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-51717 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.totolink.net/home/menu/detail/menu_listtpl/download/id/190/ids/36.htmlCVE reference, mitre
- https://www.totolink.net/CVE reference, mitre
- https://github.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.mdCVE reference, mitre
- https://github.com/ShengWu00/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.