Cyber Resilience

CVE-2025-61045

RCE in Totolink X18 Firmware 9.1.0cu.2053_b20230309

Published
01 October 2025
Modified
21 October 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 73th percentile
Risk Priority 77 floored blend · peak EPSS

Summary

CVE-2025-61045 is a critical-severity Command Injection (CWE-77) vulnerability in Totolink X18 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 27% 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 SI-10 (Information Input Validation) — 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-61045 is a command injection vulnerability (CWE-77, CWE-78) affecting the TOTOLINK X18 router running firmware version V9.1.0cu.2053_B20230309. The flaw resides in the setEasyMeshAgentCfg function, where the mac parameter fails to properly sanitize user input, allowing attackers to inject and execute arbitrary operating system commands. With a CVSS v3.1 base score of 9.8 (Critical), it enables network-accessible exploitation with low complexity and no authentication or user interaction required.

An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted request to the affected endpoint over the network. Successful exploitation grants high-impact remote code execution, compromising confidentiality, integrity, and availability (C:H/I:H/A:H) on the targeted device, potentially leading to full control over the router, data theft, or use as a pivot for further network attacks.

Mitigation details and proof-of-concept exploitation information are available in the referenced advisory at https://github.com/ilovekeer/IOT/blob/main/TOTOLINK/X18/setEasyMeshAgentCfg/1.md. Security practitioners should check for firmware updates from TOTOLINK and apply network segmentation or firewall rules to block unauthorized access to the affected function until patched.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

TOTOLINK X18 V9.1.0cu.2053_B20230309 was discovered to contain a command injection vulnerability via the mac parameter in the setEasyMeshAgentCfg function.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-10966Same product: Totolink X18
CVE-2025-1339Same product: Totolink X18
CVE-2025-1829Same product: Totolink X18
CVE-2025-61044Same product: Totolink X18
CVE-2023-29799Same product: Totolink X18
CVE-2023-29803Same product: Totolink X18
CVE-2023-29798Same product: Totolink X18
CVE-2023-29802Same product: Totolink X18
CVE-2025-29209Same product: Totolink X18
CVE-2023-29801Same product: Totolink X18

Affected Assets

totolink
x18 firmware
9.1.0cu.2053_b20230309

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Least privilege reduces the permissions available to any process that could be subverted by injected commands.

Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.

Secure engineering principles include proper neutralization and safe command construction practices.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

PR.PS-02 partial match
prevents

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

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.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References