Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach X300 management interface
-
DeliverySubmit crafted Host parameter to IPPingDiagnostics
-
ExploitInject shell metacharacters into process_ping
-
ExecutionOS command executes as service user
-
ImpactFull device compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to the TOZED X300 IP Ping Diagnostics feature (the process_ping function of the IPPingDiagnostics Handler), typically exposed through the device's web management interface. The attacker supplies OS shell metacharacters in the Host argument of the ping diagnostic request; no authentication is required (CVSS PR:N) and no user interaction is needed (UI:N). The primary LIMITING factor is reachability of the management/diagnostics interface: on CPE devices this is frequently bound to the LAN or an administrative VLAN rather than the WAN, so internet-wide exploitation depends on whether the diagnostics UI is exposed externally. Only versions up to and including 6.01.3 are affected, and no vendor patch is currently available. |
| Impact | All severity signals converge on maximum severity: the provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) scores 10.0 and describes remote, unauthenticated, low-complexity exploitation with high impact to confidentiality, integrity, and availability, which is fully consistent with the CWE-78 OS command injection described in the process_ping/IPPingDiagnostics handler. There are no conflicting signals between the vector and the description - both point to trivial remote code execution via the manipulated Host argument. However, several decision-critical signals are MISSING from the input: no EPSS probability was provided, there is no CISA KEV listing, and no SSVC decision record was supplied, so exploitation likelihood cannot be quantified from this data. No public exploit was identified at time of analysis - note that the attached GitHub security advisory (GHSA-qcpp-vfr2-v242) is filed under a DIFFERENT identifier (CVE-2026-2035703), so it should NOT be treated as confirmed POC for this CVE without manual verification. The net result is a technically maximal-severity flaw whose real-world priority is tempered by (a) the likely low deployment footprint of this CPE-class device and (b) the fact that exploitation requires reaching the device management interface, which is often not internet-exposed. Treat as high priority for any environment running TOZED X300, but the absence of EPSS/KEV means widespread opportunistic exploitation is not confirmed. |
| Exploit ScenarioDerived | An attacker with network reachability to the TOZED X300 management/diagnostics interface sends a crafted request to the IPPingDiagnostics handler, placing shell metacharacters in the Host parameter consumed by process_ping. Because the input is passed to an OS command without sanitization, the injected commands execute with the privileges of the web service (typically root on embedded CPE), yielding full device takeover. No authentication or user interaction is required per the CVSS vector; no public exploit code was identified in the provided data, though the technique is trivial to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Unauthenticated OS command injection in TOZED X300 devices up to firmware version 6.01.3 allows remote attackers to execute arbitrary operating system commands by supplying shell metacharacters in the Host argument of the IP Ping Diagnostics feature, which is typically exposed through the device's web management interface. All severity signals converge on maximum risk: the vulnerability scores 10.0 under CVSS 4.0 with high impact to confidentiality, integrity, and availability, and the vendor did not respond to disclosure and has not released a patch. Exploitation is limited primarily by whether the diagnostics interface is reachable from the attacker's network, as it is often bound to a LAN or administrative VLAN rather than the WAN; no public exploit identified at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis; the vendor was contacted but did not respond. As a compensating control, administrators should immediately restrict access to the device's web management interface, particularly the IP Ping Diagnostics feature, to trusted internal networks only. Block external access to the management port (typically HTTP/HTTPS) at the perimeter firewall, and if remote administration is required, place the device behind a VPN or a jump host. Where feasible, disable the IP Ping Diagnostics functionality entirely if it is not needed, recognizing that this reduces troubleshooting capabilities. Network segmentation to isolate IoT/CPE devices from critical assets is also advised. Monitor for exploitation attempts by reviewing web server logs for suspicious characters in the Host parameter of ping diagnostic requests. Consult the VulDB advisory at https://vuldb.com/vuln/416233 for any future updates; the referenced GitHub advisory (GHSA-qcpp-vfr2-v242) may provide additional technical details, though the presence of exploit code has not been confirmed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The TOZED X300 device exposes an IP Ping Diagnostics handler (IPPingDiagnostics) that includes a process_ping function. This function takes a user-supplied Host argument from a diagnostic request and passes it to an underlying operating system shell without proper neutralization of shell metacharacters, a classic OS command injection (CWE-78) flaw. The affected component is the web management interface, and the CPE string cpe:2.3:a:tozed:x300:*:*:*:*:*:*:*:* confirms the product but does not specify a version range; however, the description states all versions up to 6.01.3 are affected. Because the CVSS 4.0 vector includes PR:N and UI:N, no authentication or user interaction is required. The vulnerability is remotely exploitable over the network (AV:N), with low attack complexity (AC:L), and results in complete compromise of confidentiality, integrity, and availability (VC:H/VI:H/VA:H) as well as subsequent system impact (SC:H/SI:H/SA:H). The root cause is the failure to sanitize or escape the Host parameter before invoking OS commands, allowing an attacker to inject arbitrary commands that execute with the privileges of the diagnostic service.
Know when X300 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Remote unauthenticated command injection with no user interaction gives AV:N/AC:L/PR:N/UI:N; command execution yields full C/I/A impact, with scope unchanged as code runs within the same device authority.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A vulnerability was found in TOZED X300 up to 6.01.3. This vulnerability affects the function process_ping of the component IPPingDiagnostics Handler. The manipulation of the argument Host results in os command injection. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.
Technical POC Analysis
CWE-78 OS command injection.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
TOZED X300 devices running firmware up to and including 6.01.3 contain a maximum-severity command injection flaw in the IP Ping Diagnostics feature of their web management interface, allowing an attacker who can reach that interface to execute arbitrary operating system commands on the device. The vendor did not respond to disclosure and has released no patch, so affected units cannot currently be remediated at the source and must be contained through network controls. Leadership should care because these devices commonly sit on the network edge or in customer-facing deployments, where a successful compromise could give an adversary a persistent foothold for lateral movement, service disruption, and data tampering.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict the web management interface and IP Ping Diagnostics feature to a dedicated management VLAN or trusted LAN only; block WAN and cross-segment reachability at the firewall; disable the diagnostics feature if unused; deploy IDS/IPS or WAF rules alerting on shell metacharacters in the Host parameter; segment X300 devices so they cannot reach internal systems; and replace or isolate any device where these restrictions cannot be enforced. Exploitation status: no public exploit identified at time of analysis.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
EUVD-2026-96983
GHSA-f93g-mm3v-vv75
NVD
CVE.org
EPSS
VulDB
Exploit-DB