CVE-2025-70327
DoS in Totolink X5000R Firmware 9.1.0cu.2415_b20250515
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-70327 is a critical-severity Argument Injection (CWE-88) vulnerability in Totolink X5000R Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-70327 is an argument injection vulnerability affecting the TOTOLINK X5000R router running firmware version v9.1.0cu_2415_B20250515. The issue resides in the setDiagnosisCfg handler within the /usr/sbin/lighttpd executable, where the "ip" parameter is retrieved using websGetVar and passed directly to a ping command via CsteSystem without validation for inputs starting with a hyphen (-). This flaw corresponds to CWEs-88 (Improper Neutralization of Argument Delimiters in a Command) and CWE-400 (Uncontrolled Resource Consumption), earning a CVSS v3.1 base score of 9.8 (Critical: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Remote attackers can exploit this vulnerability by supplying a malicious "ip" parameter that injects arbitrary command-line options into the ping utility. Although the description specifies remote authenticated attackers, the CVSS vector indicates no privileges (PR:N) are required. Successful exploitation enables denial-of-service (DoS) conditions through excessive resource consumption or prolonged execution of the ping command.
Advisories detailing the vulnerability, including potential mitigation steps, are available in the referenced reports at https://github.com/neighborhood-H/0-DAY/blob/main/Toto-link/X5000R/SetDiagnosisCfg/report.md and https://www.notion.so/TOTOLINK-X5000R-SetDiagnosisCfg-2d170566ca7f8098a0bcee9f2a15d40d?source=copy_link. Security practitioners should consult these for vendor-specific patch information or workarounds.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207621
Vulnerability Data
TOTOLINK X5000R v9.1.0cu_2415_B20250515 contains an argument injection vulnerability in the setDiagnosisCfg handler of the /usr/sbin/lighttpd executable. The ip parameter is retrieved via websGetVar and passed to a ping command through CsteSystem without validating if the input starts with a hyphen…
more
(-). This allows remote authenticated attackers to inject arbitrary command-line options into the ping utility, potentially leading to a Denial of Service (DoS) by causing excessive resource consumption or prolonged execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.5
Mitigating Controls (NIST 800-53 r5) AI
Developer testing can discover argument-injection flaws in command-construction code but does not stop their introduction.
SC-5 directly limits the effects of resource-exhaustion events that constitute uncontrolled consumption.
SC-6 enforces explicit allocation limits on resources, structurally preventing the weakness from occurring.
Input validation directly stops construction of command strings containing unneutralized delimiters or injected arguments.
Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper input validation and command construction to prevent argument injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.
Security testing can detect argument injection but does not prevent it at the source.
A.8.6's monitoring, stress-testing, projections, tuning, demand-reduction steps (e.g. optimizing queries, deleting obsolete data, restricting non-critical bandwidth) and capacity planning directly stop most uncontrolled consumption from being exploitable by keeping resources within safe bounds; the bounded remainder is algorithmic flaws (e.g. infinite loops, uncontrolled recursion) that no amount of capacity planning can prevent from exhausting a resource when triggered.
Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.
Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.
Secure coding standards explicitly require proper neutralization of command arguments, directly eliminating CWE-88.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.