CVE-2025-55893VulnerabilityPublished 15 Dec 2025

CVE-2025-55893: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 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 2026-10-25.

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 router's management interfaces to trusted networks only, using firewall rules or VLAN segmentation to limit exposure. 2. Disable remote management features if not strictly necessary, especially from untrusted or external networks. 3. Monitor network traffic for unusual command injection patterns or unexpected configuration changes on TOTOLINK N200RE devices. 4. Implement network segmentation to isolate vulnerable devices from critical infrastructure and sensitive data environments. 5. Use strong network access controls and authentication mechanisms for device management where possible. 6. Regularly check for firmware updates or official patches from TOTOLINK and apply them promptly once available. 7. Consider replacing affected devices with models from vendors with stronger security track records if patching is delayed. 8. Educate IT staff about this vulnerability and encourage vigilance for signs of compromise. 9. Employ intrusion detection or prevention systems capable of detecting command injection attempts targeting network devices. 10. Maintain up-to-date asset inventories to quickly identify and remediate affected devices across the organization.

Description

CVE-2025-55893 is a medium severity command injection vulnerability affecting TOTOLINK N200RE routers running firmware version 9.3.5u.6437_B20230519. The flaw exists in the setOpModeCfg function via the hostName parameter, allowing an unauthenticated remote attacker with network access to execute arbitrary commands. Exploitation does not require user interaction and has low attack complexity. While the vulnerability impacts the integrity of the device, it does not affect confidentiality or availability directly. No known exploits are currently reported in the wild, and no patches have been published yet. European organizations using this router model, especially in countries with higher TOTOLINK market penetration, could be at risk. Mitigation involves network segmentation, restricting management interface access, and monitoring for suspicious activity until an official patch is released.

Impact

For European organizations, this vulnerability poses a risk primarily to the integrity of network infrastructure devices, specifically the TOTOLINK N200RE routers. Successful exploitation could allow attackers to execute arbitrary commands on the router, potentially leading to unauthorized configuration changes, installation of persistent malware, or pivoting to other internal network assets. While confidentiality and availability are not directly impacted, integrity compromise can lead to long-term security breaches and data manipulation. Organizations relying on these routers for small office or home office environments, or as part of branch office connectivity, may face increased risk. The lack of required authentication and user interaction lowers the barrier for exploitation by internal or adjacent network attackers, including malicious insiders or compromised devices. The absence of known exploits in the wild reduces immediate threat but does not eliminate the risk, especially as public disclosure may prompt attackers to develop exploits. European entities with limited network segmentation or remote management exposure are particularly vulnerable.

Summary

CVE-2025-55893 identifies a command injection vulnerability in the TOTOLINK N200RE router firmware version 9.3.5u.6437_B20230519. The vulnerability resides in the setOpModeCfg function, specifically through the hostName parameter, which fails to properly sanitize input. This allows an unauthenticated attacker with access to the network interface to inject arbitrary commands that the device executes with elevated privileges. The vulnerability is categorized under CWE-77 (Improper Neutralization of Special Elements used in a Command), indicating that input validation is insufficient to prevent command injection attacks. The CVSS v3.1 base score is 6.5, reflecting medium severity, with attack vector being adjacent network (AV:A), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), no confidentiality impact (C:N), high integrity impact (I:H), and no availability impact (A:N). This means an attacker within the local network or connected via VPN could exploit this vulnerability without authentication or user interaction, potentially executing arbitrary commands that compromise the device's integrity. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and should be considered a significant risk for affected deployments.

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:19 UTC

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats