VulnerabilityPublished 8 Dec 2025Updated 24 Feb 2026

CVE-2025-14276: Ilevia EVE X1 Server · Command Injection

Affects Ilevia EVE X1 ServerSource CVE Database V5

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.3Medium

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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 or the CVSS exploit maturity 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

Upgrade the Ilevia EVE X1 Server to the latest version where this vulnerability is patched.
Restrict network access to the affected service by closing or firewalling the port used by the /ajax/php/leaf_search.php endpoint, especially from untrusted external networks.
Implement network segmentation to isolate the EVE X1 Server from the internet and less trusted network zones.
Monitor server logs for unusual command execution attempts or suspicious input patterns targeting the vulnerable endpoint.
Employ web application firewalls (WAFs) with custom rules to detect and block command injection attempts against the vulnerable script.
Conduct regular vulnerability scans and penetration tests to verify the effectiveness of mitigations.
Educate system administrators on the importance of timely patching and minimizing exposed services.
If patching is delayed, consider disabling or restricting access to the vulnerable functionality if feasible.

Description

A vulnerability was determined in Ilevia EVE X1 Server up to 4.6.5.0.eden. Impacted is an unknown function of the file /ajax/php/leaf_search.php. This manipulation of the argument line causes command injection. The attack can be initiated remotely. A high degree of complexity is needed for the attack. The exploitability is considered difficult. The exploit has been publicly disclosed and may be utilized. Upgrading the affected component is recommended. The vendor confirms the issue and recommends: "We already know that issue and on most devices are already solved, also it’s not needed to open the port to outside world so we advised our customer to close it".

Impact

If exploited, this vulnerability could allow remote attackers to execute arbitrary commands on the affected server, potentially leading to unauthorized access, data leakage, or disruption of service. Although the impact on confidentiality, integrity, and availability is rated low individually, the ability to execute commands remotely without authentication poses a significant risk of system compromise. The high complexity required for exploitation limits immediate widespread attacks, but targeted attackers with sufficient skill could leverage this flaw to gain control over critical infrastructure or sensitive data. Organizations relying on Ilevia EVE X1 Server in critical environments may face operational disruptions and reputational damage if exploited. The lack of known exploits in the wild currently reduces immediate risk, but the public disclosure means attackers may develop exploits over time, increasing threat levels.

Summary

CVE-2025-14276 identifies a command injection vulnerability in the Ilevia EVE X1 Server, affecting versions up to 4.6.5.0.eden. The vulnerability resides in an unspecified function within the /ajax/php/leaf_search.php script, where improper validation or sanitization of input parameters allows an attacker to inject and execute arbitrary system commands remotely. This type of vulnerability can lead to full system compromise if successfully exploited. The attack vector is network-based, requiring no authentication or user interaction, but the complexity of crafting a successful exploit is high, reducing the likelihood of widespread exploitation. The vendor has confirmed the vulnerability and indicated that many devices have already been patched. They also advise customers to close external ports to the affected service to reduce attack surface. The CVSS 4.0 vector (AV:N/AC:H/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects a medium severity with network attack vector, high attack complexity, no privileges or user interaction required, and low impact on confidentiality, integrity, and availability. No known exploits are currently active in the wild, but public disclosure increases risk over time. Organizations running the affected versions should prioritize patching and network segmentation to mitigate risk.

References

Community reviews

Loading reviews…