CVE-2025-5904
Published: 10 June 2025
Summary
CVE-2025-5904 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Totolink T10 Firmware. Its CVSS base score is 7.4 (High).
Operationally, ranked in the top 19.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
A buffer overflow vulnerability exists in the TOTOLINK T10 firmware version 4.1.8cu.5207. It resides in the setWiFiMeshName function within the POST Request Handler component at /cgi-bin/cstecgi.cgi, where unsanitized input to the device_name argument can trigger memory corruption. The issue is tracked under CWE-119 and CWE-120 and carries a CVSS 4.0 score of 7.4.
Remote attackers who can reach the web interface with valid low-privileged credentials may send a crafted POST request to execute arbitrary code or crash the device, resulting in full compromise of confidentiality, integrity, and availability on the affected system. A functional exploit has already been published.
The EPSS score remains low and essentially flat at approximately 0.014, indicating limited observed exploitation interest since disclosure. No vendor advisory or patch information is available from the listed references.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-17609
Vulnerability details
A vulnerability was found in TOTOLINK T10 4.1.8cu.5207. It has been declared as critical. Affected by this vulnerability is the function setWiFiMeshName of the file /cgi-bin/cstecgi.cgi of the component POST Request Handler. The manipulation of the argument device_name leads to…
more
buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.