A vulnerability was identified in TOTOLINK A800R 4.1.2cu.5137_B20200730. This impacts the function setUrlFilterRules of the file /cgi-bin/cstecgi.cgi of the component firewall.so. The manipulation of the argument url leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit is publicly available and might be used.
Security readout for executives and security teams
Plain-English summary
A flaw in one TOTOLINK A800R firmware release can let an authenticated remote user overflow router memory through its management interface. Successful exploitation could compromise confidentiality, integrity, and availability. Public proof-of-concept material raises near-term risk, but the supplied sources do not establish active exploitation or identify a vendor fix.
Executive priority
Treat as an urgent network-edge exposure review. Locate affected routers immediately, reduce management access, and seek vendor-supported remediation. Prioritize externally manageable devices, while recognizing that public proof-of-concept availability is not evidence of active exploitation.
Technical view
CVE-2026-19846 is a stack-based buffer overflow in firewall.so's setUrlFilterRules function, reached through /cgi-bin/cstecgi.cgi when processing the url argument. The listed CVSS 2.0 vector scores 9.0 and indicates network reachability, low complexity, required authentication, and potentially complete confidentiality, integrity, and availability impact.
Likely exposure
Confirmed scope is limited to TOTOLINK A800R firmware 4.1.2cu.5137_B20200730. Risk is greatest where the management CGI endpoint is reachable by untrusted or compromised authenticated users. The bundle does not establish whether other versions are affected or whether internet exposure is enabled by default.
Exploitation context
A public proof of concept is referenced, and remote initiation is reported. The CVSS vector indicates authentication is required. The CVE is not listed as KEV in the supplied bundle, and no cited evidence confirms exploitation in the wild.
Researcher notes
CWE-119 and CWE-121 classifications support an improper memory-boundary and stack-overflow finding. Available details identify the function, CGI path, argument, and exact firmware, but do not document vendor patch status, affected-version range, default exposure, observed attacks, or reliable indicators of compromise.
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.
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.
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
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: 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.
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.
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.