Totolink A8000RU EUVD-2026-31597

Exploitation requires network reachability to the router's Web Management Interface on the HTTP(S) admin port and the ability to issue a POST to /cgi-bin/cstecgi.cgi invoking the setTracerouteCfg endpoint with a crafted 'command' argument. Per CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:N), no authentication, user interaction, or non-default configuration is needed against firmware 7.1cu.643_b20200521. The principal limiting factor is exposure of the management interface: in default deployments the admin UI is LAN-only, so Internet-based exploitation requires that the user has explicitly enabled remote/WAN administration, while LAN-local exploitation requires only foothold on the same broadcast segment (e.g., a compromised IoT device or guest Wi-Fi).

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H) scores 8.9 and indicates a remote, low-complexity, unauthenticated path to full confidentiality, integrity, and availability impact - among the worst possible exploitation profiles. The E:P (Proof-of-Concept) metric and the GitHub-hosted README walkthrough corroborate that publicly available exploit code exists. However, EPSS at 0.89% (76th percentile) is moderate rather than elevated, and the CVE is not in CISA KEV, suggesting no observed mass exploitation yet - consistent with the A8000RU being a relatively niche SOHO router. The realistic risk is therefore high for any device whose web interface is reachable from the WAN or from an untrusted LAN segment, but lower for properly segmented deployments. Note that VulDB is the sole originating reporter and there is no vendor advisory at the time of analysis, so the disclosure is essentially one-sourced.

An attacker on the same network (or the Internet, if remote management is enabled) sends a crafted HTTP POST to /cgi-bin/cstecgi.cgi invoking the setTracerouteCfg action with a shell metacharacter payload in the 'command' field, causing the router to execute attacker-supplied commands as the web server's user (typically root on this class of device). Because publicly available exploit code exists in the referenced GitHub repository, weaponization requires minimal effort and yields a foothold suitable for installing botnet implants or pivoting into the internal network.