LiveActive security incident?Get immediate response
CVE Record

CVE-2026-85031: TOTOLINK CP450 cstecgi.cgi buffer overflow

A vulnerability was found in TOTOLINK CP450 4.1.0. The impacted element is an unknown function of the file /cgi-bin/cstecgi.cgi. Performing a manipulation of the argument topicurl results in buffer overflow. Remote exploitation of the attack is possible.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

TOTOLINK CP450 firmware 4.1.0 contains a remotely reachable memory-safety flaw. A user with low-level privileges may trigger a buffer overflow through a device CGI endpoint, potentially disrupting the device or compromising its confidentiality and integrity. Public evidence does not confirm active exploitation.

Executive priority

Treat confirmed CP450 4.1.0 deployments as an urgent remediation priority, especially when management access is externally reachable. Reduce exposure immediately while seeking vendor guidance. No active exploitation is established, but the reported impact and low attack complexity justify rapid inventory, isolation, and update decisions.

Technical view

The flaw affects /cgi-bin/cstecgi.cgi when processing the topicurl argument. Improper bounds handling can cause a buffer overflow, classified as CWE-119 and CWE-120. The supplied CVSS 3.1 vector scores 9.9: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Confirmed scope is limited to TOTOLINK CP450 firmware 4.1.0. Devices are most exposed when their management or CGI interface is reachable from untrusted networks or accessible to low-privileged accounts. The bundle does not establish whether other firmware versions or TOTOLINK products are affected.

Exploitation context

Remote exploitation is reported as possible and requires low privileges. The CVSS vector marks exploit maturity as proof-of-concept, but the bundle provides no independently verified exploit details. The CVE is not listed as KEV, and no supplied source confirms active exploitation in the wild.

Researcher notes

The public description does not identify the vulnerable function, exact bounds error, affected architecture, execution outcome, or corrected release. Avoid assuming reliable code execution from the overflow alone. Validate reachability and authentication requirements defensively; consult the CVE record and VulDB entry for updates without reproducing offensive payloads.

Mitigation direction

  • Identify CP450 devices running firmware 4.1.0.
  • Restrict management access to trusted administrative networks and authorized accounts.
  • Disable external access to the CGI management interface where operationally feasible.
  • Review TOTOLINK guidance for corrected firmware or vendor-supported mitigation.
  • Consider isolating or replacing devices if no supported correction is available.

Validation and detection

  • Inventory CP450 hardware and record its installed firmware version.
  • Verify whether /cgi-bin/cstecgi.cgi is reachable from untrusted networks.
  • Review firewall, reverse-proxy, and access-control rules protecting management interfaces.
  • Check device logs for unusual requests involving cstecgi.cgi or topicurl.
  • Confirm any vendor update or mitigation through controlled, non-destructive testing.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cwe · low confidence lookup

CWE-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 lookup
cve · low confidence lookup

CVE-2026-85031 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R

Official CVE source material

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.

4CVSS vectors
6Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

4 official scores

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R3.16VulDB
9.9CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R3.16VulDB
9.4CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P——VulDB
9CVSS 2.0CriticalAV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR810VulDB

Vulnerability scoring details

Base CVSS 4.0 score

9.4Critical
CVSS 4.0 vector shape for CVE-2026-85031Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TOTOLINKCP4504.1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

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.

CWE-120 · source CWE mapping

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.