CVE-2025-60738
7.5Ilevia · EVE X1 Server
A remote code execution vulnerability in the Ilevia EVE X1 Server allows unauthenticated attackers to execute arbitrary code by exploiting improper input validation in the ping.php component.
Executive summary
The Ilevia EVE X1 Server is vulnerable to unauthenticated remote code execution, posing a critical risk to system integrity and availability.
Vulnerability
This vulnerability occurs because the ping.php component fails to perform secure filtering on IP parameters. An unauthenticated remote attacker can supply malicious input to this parameter to achieve arbitrary code execution.
Business impact
Successful exploitation of this vulnerability grants an attacker full control over the affected EVE X1 Server, potentially leading to unauthorized data access, total system compromise, and lateral movement within the network. With a CVSS score of 7.5, this high-severity flaw requires immediate attention to prevent operational disruption and the potential exfiltration of sensitive configuration data.
Remediation
Immediate Action: Restrict network access to the EVE X1 Server to trusted IP addresses only, and contact Ilevia support immediately to verify if a patch is available for your specific firmware and logic versions.
Proactive Monitoring: Monitor server access logs for anomalous requests to the ping.php endpoint, particularly those containing shell metacharacters or unexpected IP address formats.
Compensating Controls: Deploy a Web Application Firewall (WAF) or an intrusion prevention system to block requests containing malicious command injection patterns directed at the ping.php interface.
Exploitation status
Public Exploit Available: Yes — a public proof-of-concept exists as documented in the research repository referenced by the CVE record.
Analyst recommendation
Given the availability of a proof-of-concept and the ease of exploitation via the network vector, administrators must prioritize the protection of the EVE X1 Server. If a vendor patch is not immediately applicable, the device should be isolated from the public internet until appropriate security controls or updates are implemented to mitigate the risk of remote code execution.