Skip to main content

TOTOLINK A3300R CVE-2025-12258

HIGH
Buffer Overflow (CWE-119)
2025-10-27 cna@vuldb.com
8.7
CVSS 4.0 · Vendor: vuldb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach A3300R web interface with credentials
  2. Delivery
    Send crafted POST to /cgi-bin/cstecgi.cgi
  3. Exploit
    Overflow stack buffer via 'opmode' parameter
  4. Execution
    Execute arbitrary code on router
  5. Impact
    Full device compromise or DoS

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires reaching the device's HTTP management interface at /cgi-bin/cstecgi.cgi and invoking the setOpModeCfg handler with a manipulated 'opmode' POST parameter; per the CVSS vector (PR:L), the attacker needs a valid authenticated session on the router before the overflow can be triggered. The primary limiting factors are: (1) authentication is required, so the management UI credentials (default or configured) must be known or obtainable; and (2) the management interface must be network-reachable from the attacker - typically LAN-side by default, becoming remotely exploitable only where remote/WAN administration is enabled or the panel is otherwise exposed. Only the specific firmware build 17.0.0cu.557_B20221024 on the A3300R is confirmed affected.

Impact

Signals are moderately consistent and point to a real but not top-tier priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable, low-complexity attack that nonetheless requires some level of authentication (PR:L), with full high impact to confidentiality, integrity, and availability on the device (VC:H/VI:H/VA:H) - scope-contained to the router itself. A publicly available proof-of-concept exists on GitHub, which lowers the barrier to opportunistic use, but the vulnerability is NOT in CISA KEV, so there is no confirmed active exploitation. The EPSS score of 1.02% (62nd percentile) is low-to-moderate and is consistent with the absence of KEV listing - together they suggest that, despite public POC code, this is not seeing broad automated exploitation, likely because it is a single consumer-router model with a limited footprint and requires authentication. The practical risk concentration is on internet-exposed A3300R management interfaces; the PR:L requirement meaningfully limits purely anonymous mass exploitation, though SOHO routers frequently ship with weak or default credentials that can erode that barrier.

Exploit ScenarioDerived

An attacker with access to the A3300R web management interface (reachable over the network and, if the admin panel is WAN-exposed or reachable from the LAN, by a remote actor) sends a crafted POST request to /cgi-bin/cstecgi.cgi invoking setOpModeCfg with an overlong 'opmode' argument. This overflows a stack buffer, allowing the attacker to crash the device or execute arbitrary code in the router's context. A public POC for this exact endpoint is available on GitHub (noahze01/IoT-vulnerable), reducing the effort required to reproduce the attack.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 1.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Stack-based buffer overflow in the TOTOLINK A3300R router firmware (build 17.0.0cu.557_B20221024) allows remote attackers to corrupt memory via the 'opmode' POST parameter handled by setOpModeCfg in /cgi-bin/cstecgi.cgi. Per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N), exploitation requires a valid authenticated management session and network reachability to the device's HTTP administration interface - the overflow is not reachable pre-authentication, and the panel is LAN-side by default, becoming remotely exploitable only where WAN/remote administration is enabled or the interface is otherwise exposed. Publicly available exploit code exists (proof-of-concept published on GitHub), but there is no indication of confirmed active exploitation (not in CISA KEV), and EPSS places likelihood at roughly 1.02% (62nd percentile) - a real but not top-tier priority for most environments.

RemediationAI

No vendor-released patch was identified at time of analysis: the available references point to the TOTOLINK homepage (https://www.totolink.net/) and to VulDB records (https://vuldb.com/?id.329929, https://vuldb.com/?ctiid.329929, https://vuldb.com/?submit.673725) plus the public proof-of-concept (https://github.com/noahze01/IoT-vulnerable/blob/main/TOTOLink/A3300R/setOpModeCfg.md), but none of them contain a fixed firmware version, so users should check TOTOLINK support for a newer A3300R build than 17.0.0cu.557_B20221024 and upgrade if one becomes available. In the meantime, apply compensating controls that directly shrink the attack surface: disable the router's remote/WAN management so the /cgi-bin/cstecgi.cgi panel is reachable only from the LAN (this removes the internet-facing vector entirely but requires local or VPN access for administration); if remote management cannot be turned off, restrict access to the management port with firewall/ACL rules limited to trusted source IPs (accepting that any reachable and authenticated user can still trigger the overflow); and replace default or weak administrative credentials with strong unique ones and change the management port/disable unused services, since the attacker must already hold a valid session (PR:L) before the 'opmode' buffer overflow can be reached. Segmenting or isolating the router's management VLAN from untrusted hosts further limits who can authenticate, and monitoring for anomalous POST requests to /cgi-bin/cstecgi.cgi with oversized 'opmode' values can provide detection while no patched firmware is confirmed.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the CGI POST parameter handler on the TOTOLINK A3300R, a consumer/SOHO Wi-Fi router. The vulnerable function, setOpModeCfg, is invoked through the web management endpoint /cgi-bin/cstecgi.cgi and processes the 'opmode' parameter supplied in an HTTP POST body. The root cause class is CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer): the handler copies attacker-controlled input into a fixed-size stack buffer without adequate length validation, producing a classic stack-based buffer overflow. Successful corruption of the saved return address or adjacent stack data can subvert control flow and yield arbitrary code execution with the privileges of the underlying CGI/HTTP daemon. CPE data (cpe:2.3:o:totolink:a3300r_firmware:17.0.0cu.557_b20221024:*:*:*:*:*:*:*) confirms that only this specific firmware build on the A3300R is validated as affected; the firmware is distributed as the router's embedded OS image rather than a standalone application. Because the overflow lives in the management-plane CGI, reachability is governed entirely by how the HTTP admin interface is exposed (LAN-only by default versus WAN-exposed when remote management is turned on), which combined with the PR:L authentication requirement caps the real-world attack surface relative to a fully pre-auth, internet-facing flaw.

Know when A3300R Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Network-reachable CGI endpoint (AV:N) with a simple overlong parameter (AC:L) but requiring an authenticated session (PR:L); memory-corruption code execution yields full device C/I/A impact, scope unchanged.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (vuldb).

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A vulnerability was detected in TOTOLINK A3300R 17.0.0cu.557_B20221024. Impacted is the function setOpModeCfg of the file /cgi-bin/cstecgi.cg of the component POST Parameter Handler. The manipulation of the argument opmode results in stack-based buffer overflow. The attack may be performed from remote.

Executive ViewAI

Why It Matters

The TOTOLINK A3300R router running firmware build 17.0.0cu.557_B20221024 is affected by a high-severity security flaw that could allow an authenticated attacker with access to the management interface to compromise the device. Publicly available exploit code exists, but there is no confirmed active exploitation, and default LAN-side restrictions limit exposure; however, organizations that have enabled remote administration or exposed the HTTP panel face potential device takeover, network disruption, and lateral movement. Leadership should prioritize identifying exposed devices and restricting management access, because no vendor-released patch identified at time of analysis.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable WAN/remote administration and block inbound HTTP management access; restrict the admin interface to trusted LAN/VPN only; enforce strong unique credentials and disable default accounts; segment router management traffic; monitor for exploit attempts against /cgi-bin/cstecgi.cgi and the 'opmode' parameter; consider IDS/IPS or WAF signatures; replace or retire the device if exposure cannot be eliminated and vendor support is unavailable.

Threat Intelligence Overview

EPSS Score
1.0%
Top 38% exploitable
Prevalence
Low
single budget SOHO router model, limited and consumer-only deployment footprint
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 1.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

65
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Affected Products (CPE)CVE.org

cpe:2.3:o:totolink:a3300r_firmware:17.0.0cu.557_b20221024:*:*:*:*:*:*:*
CVE-2024-24333 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the desc paramet

CVE-2024-24332 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the url paramete

CVE-2024-24331 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the enable param

CVE-2024-24330 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the port or enab

CVE-2024-24329 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the enable param

CVE-2024-24328 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the enable param

CVE-2024-24327 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the pppoePass pa

CVE-2024-24326 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the arpEnable pa

CVE-2024-24325 CRITICAL POC
9.8 Jan 30

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the enable param

CVE-2023-46993 CRITICAL POC
9.8 Oct 31

In TOTOLINK A3300R V17.0.0cu.557_B20221024 when dealing with setLedCfg request, there is no verification for the enable

CVE-2023-46976 CRITICAL POC
9.8 Oct 31

TOTOLINK A3300R 17.0.0cu.557_B20221024 contains a command injection via the file_name parameter in the UploadFirmwareFil

CVE-2023-37173 CRITICAL POC
9.8 Jul 07

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the command para

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy