Security readout for executives and security teams
Plain-English summary
Certain ToToLink router firmware can mishandle an unauthenticated web request. A long IpAddress value may overwrite memory in the device's web component, causing corruption or possible code execution. Business risk is highest where affected router administration interfaces are reachable from untrusted networks.
Executive priority
Treat as a moderate-priority network edge risk. Prioritize any affected router with reachable management access, because exploitation is unauthenticated and could affect device availability or control.
Technical view
The issue is CWE-121 in cstecgi.cgi setDefResponse: the IpAddress parameter is copied with strcpy into a fixed stack buffer without length validation. Sources identify LR1200GB V9.1.0u.6619_B20230130 and NR1800X V9.1.0u.6681_B20230703. Impact is described as memory corruption or potential arbitrary code execution without authentication.
Likely exposure
Exposure appears limited to organizations using the named ToToLink LR1200GB or NR1800X firmware builds, especially where router web management is reachable from LAN, guest, VPN, or internet-facing networks.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Public researcher material exists, but this assessment does not infer weaponized exploitation from that alone.
Researcher notes
Evidence is specific about the vulnerable function, parameter, unsafe strcpy use, and two firmware builds. The source bundle does not provide a vendor fix, CPE mapping, or confirmed exploitation evidence, so remediation should follow current ToToLink guidance.
Mitigation direction
- Identify affected ToToLink LR1200GB and NR1800X firmware versions.
- Restrict router web management to trusted administrative networks only.
- Disable internet-facing management access where present.
- Check ToToLink guidance for fixed firmware or vendor mitigations.
- Replace or retire devices if no supported fix is available.
Validation and detection
- Inventory router models and firmware versions against the named builds.
- Review firewall rules for exposed router web management interfaces.
- Check management logs for unusual requests involving IpAddress parameters.
- Confirm whether ToToLink has published updated firmware guidance.
- Track CVE and KEV sources for exploitation status changes.
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-121: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-60688 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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:L/I:N/A:L3.92.5CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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/CVE reference, mitre
- https://github.com/yifan20020708/SGTaint-0-day/blob/main/ToToLink/ToToLink-LR1200GB/CVE-2025-60688.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.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.