Cyber Resilience

CVE-2025-3249

Command Injection in Totolink A6000R Firmware 1.0.1-b20201211.2000

Published
04 April 2025
Modified
28 May 2025
Patch / advisory
CVSS Score v4 5.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.026 84th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-3249 is a medium-severity Injection (CWE-74) vulnerability in Totolink A6000R Firmware. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 16% 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.

A critical command injection vulnerability, tracked as CVE-2025-3249 and assigned CWE-74 and CWE-77, affects the TOTOLINK A6000R router running firmware 1.0.1-B20201211.2000. The flaw resides in the apcli_cancel_wps function within /usr/lib/lua/luci/controller/mtkwifi.lua, where unsanitized input allows arbitrary command execution.

An authenticated remote attacker can supply crafted parameters to the affected endpoint and execute operating-system commands on the device. The CVSS 5.3 vector reflects network attack reachability with low attack complexity and low privileges required, resulting in limited impacts to confidentiality, integrity, and availability on the target router.

Public references include a detailed proof-of-concept on GitHub and entries on VulDB, but no vendor advisory or firmware patch addressing the issue has been published by TOTOLINK. The associated EPSS score remains low, moving only modestly from 0.0637 to a peak of 0.0721.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability classified as critical was found in TOTOLINK A6000R 1.0.1-B20201211.2000. Affected by this vulnerability is the function apcli_cancel_wps of the file /usr/lib/lua/luci/controller/mtkwifi.lua. The manipulation leads to command injection. The attack can be launched remotely. The exploit has been disclosed…

more

to the public and may be used.

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.
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.
T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-57212Same product: Totolink A6000R
CVE-2024-41320Same product: Totolink A6000R
CVE-2024-57214Same product: Totolink A6000R
CVE-2024-57211Same product: Totolink A6000R
CVE-2024-57213Same product: Totolink A6000R
CVE-2024-41318Same product: Totolink A6000R
CVE-2024-41316Same product: Totolink A6000R
CVE-2024-41319Same product: Totolink A6000R
CVE-2026-1548Same vendor: Totolink
CVE-2026-1326Same vendor: Totolink

Affected Assets

totolink
a6000r firmware
1.0.1-b20201211.2000

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.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

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

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

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 output encoding that prevent injection flaws.

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.

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 injection vulnerabilities before release.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

prevents

Application security requirements explicitly call for controls against injection attacks in software design.

References