VulnerabilityPublished 15 Dec 2025

CVE-2025-55901: Command Injection

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately restrict access to the TOTOLINK A3300R router management interfaces to trusted networks only, using firewall rules or VLAN segmentation. 2. Disable remote management features if not strictly necessary to reduce exposure. 3. Monitor network traffic and device logs for unusual commands or behavior indicative of exploitation attempts. 4. Implement network segmentation to isolate vulnerable devices from sensitive systems. 5. Use network intrusion detection systems (NIDS) with signatures or heuristics to detect command injection patterns targeting NTPSyncWithHost or related functions. 6. Engage with TOTOLINK support channels to obtain information on forthcoming patches or firmware updates and apply them promptly once available. 7. Consider temporary replacement or upgrade of affected devices in high-risk environments. 8. Educate network administrators about the vulnerability and ensure incident response plans include steps for this specific threat.

Description

CVE-2025-55901 is a medium-severity command injection vulnerability affecting TOTOLINK A3300R routers running firmware version V17.0.0cu.596_B20250515. The flaw exists in the NTPSyncWithHost function via the host_time parameter, allowing an unauthenticated remote attacker to execute arbitrary commands. The vulnerability requires network access but no user interaction or privileges. Exploitation could lead to integrity compromise of the device, potentially enabling attackers to alter device behavior or network traffic. No known exploits have been reported in the wild, and no patches are currently available. European organizations using this router model may face risks, especially in environments relying on these devices for network connectivity. Mitigation involves network segmentation, restricting access to the router’s management interfaces, and monitoring for suspicious activity until a vendor patch is released.

Impact

For European organizations, exploitation of this vulnerability could undermine the integrity of network infrastructure by allowing attackers to execute arbitrary commands on affected TOTOLINK A3300R routers. This could lead to unauthorized configuration changes, interception or redirection of network traffic, or use of the device as a pivot point for lateral movement within corporate networks. Given the router’s role in providing connectivity, disruption or compromise could impact business operations, especially in SMEs or organizations relying on this hardware for critical network functions. The lack of confidentiality impact reduces the risk of direct data leakage, but integrity compromise can facilitate more severe attacks. Organizations in sectors with high network security requirements, such as finance, healthcare, or critical infrastructure, may face elevated risks. The absence of known exploits provides a window for proactive mitigation, but the medium severity and ease of exploitation warrant urgent attention.

Summary

CVE-2025-55901 identifies a command injection vulnerability in the TOTOLINK A3300R router firmware version V17.0.0cu.596_B20250515. The vulnerability resides in the NTPSyncWithHost function, specifically through improper sanitization of the host_time parameter. This parameter is used in a context that allows injection of arbitrary commands, classified under CWE-77 (Improper Neutralization of Special Elements used in a Command). An attacker with network access can exploit this flaw without requiring authentication or user interaction, making it remotely exploitable. The CVSS v3.1 score is 6.5 (medium), reflecting the lack of confidentiality impact but high integrity impact, as attackers can execute commands that may alter device configuration or behavior. The attack vector is adjacent network (AV:A), meaning the attacker must be on the same network or connected via VPN or similar means. No patches or official fixes have been published yet, and no known exploits are reported in the wild. This vulnerability could be leveraged to compromise the router, potentially enabling further network attacks or persistent footholds within affected environments.

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Dec 2025, 18:20 UTC

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats