Security readout for executives and security teams
Plain-English summary
CVE-2026-1328 affects Totolink NR1800X firmware version 9.1.0u.6279_B20210910. A malformed SSID value in a web configuration request can trigger a buffer overflow. Sources rate it critical and say a public exploit exists. KEV does not list active exploitation, so treat this as urgent exposure management, not confirmed in-the-wild compromise.
Executive priority
Prioritize within the next maintenance cycle, faster for internet-exposed or business-critical sites. The combination of critical severity and public exploit availability creates material risk, even without confirmed active exploitation. If no vendor fix is available, reduce exposure immediately and plan replacement or isolation.
Technical view
The issue is in setWizardCfg within /cgi-bin/cstecgi.cgi, part of the POST request handler. Manipulation of the ssid argument can cause a buffer overflow, mapped to CWE-119 and CWE-120. The CVSS v2 score is 9.0 with network attack vector, low complexity, and authenticated access indicated by the vector.
Likely exposure
Exposure is most relevant for organizations using Totolink NR1800X devices on firmware 9.1.0u.6279_B20210910. Risk increases if the device management interface is reachable from untrusted networks or weakly controlled internal networks. Evidence provided does not identify other affected models or firmware versions.
Exploitation context
The source bundle states remote exploitation is possible and that exploit material is public. The CVSS vector indicates authentication is required. There is no KEV listing and no cited evidence of active exploitation. Public exploit availability raises urgency for rapid inventory, access restriction, and vendor guidance review.
Researcher notes
Source evidence centers on VulDB and the CVE record. The public details identify the vulnerable endpoint, function, parameter, affected firmware, and buffer overflow class. Avoid assuming unauthenticated exploitation because the provided CVSS vector includes Au:S. Patch status is not established in the provided sources.
Mitigation direction
- Identify Totolink NR1800X devices and confirm firmware versions.
- Restrict management access to trusted administrative networks only.
- Disable internet exposure of the device administration interface.
- Review Totolink guidance for fixed firmware or official mitigations.
- Use strong administrative credentials and remove unused accounts.
- Replace or isolate affected devices if no vendor fix is available.
Validation and detection
- Check asset inventory for Totolink NR1800X devices.
- Verify whether firmware equals 9.1.0u.6279_B20210910.
- Confirm the management interface is not internet-accessible.
- Review logs for unusual setWizardCfg or SSID configuration activity.
- Monitor VulDB, CVE, and Totolink pages for updates.
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-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-1328 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 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
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.
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.
AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR810Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
9CriticalVector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-342304 | Totolink NR1800X POST Request cstecgi.cgi setWizardCfg buffer overflowCVE reference · vdb-entry, technical-description
- VDB-342304 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #735792 | TOTOLINK NR1800X NR1800X_Firmware V9.1.0u.6279_B20210910 Buffer OverflowCVE reference · third-party-advisory
- https://lavender-bicycle-a5a.notion.site/TOTOLINK-NR1800X-setWizardCfg-2e453a41781f80568a54c9368082fbe9?source=copy_linkCVE reference · exploit
- https://www.totolink.net/CVE reference · product
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 Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.