CVE-2026-124057

TOTOLINK CA300-PoE cstecgi.cgi setWiFiMultipleConfig buffer overflow

  • Critical 9.4
  • A public exploit reference is listed

Description

A security flaw has been discovered in TOTOLINK CA300-PoE 6.2c.884. This impacts the function setWiFiMultipleConfig of the file /cgi-bin/cstecgi.cgi. Performing a manipulation of the argument Key1Str1 results in buffer overflow. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks.

Key facts

Published
7 Nov 2026
Last changed
11 Nov 2026
Assigned by
VulDB
EPSS
0.635% likely to be exploited in the next 30 days, higher than 51.038% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.4CVSS 4.0, Criticalfrom the CNA (VulDB)CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P
  • 9.1CVSS 3.1, Criticalfrom the CNA (VulDB)CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C
  • 9.1CVSS 3.0, Criticalfrom the CNA (VulDB)CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C
  • 8.3CVSS 2.0, Highfrom the CNA (VulDB)AV:N/AC:L/Au:M/C:C/I:C/A:C/E:POC/RL:ND/RC:C

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
TOTOLINKCA300-PoE
  • 6.2c.884 (affected)

Timeline

  1. 6 Nov 2026 Advisory disclosed
  2. 6 Nov 2026 VulDB entry created
  3. 6 Nov 2026 VulDB entry last update
  4. 7 Nov 2026 Published

Weakness

References