---
title: "What's New: CVE Resolution"
canonical: "https://help.agiloft.com/space/HELP/43718162/What's+New%3A+CVE+Resolution"
format: markdown
---
As part of our ongoing commitment to transparency and security, here you can find details of four vulnerabilities (CVEs) that were recently identified and resolved in Agiloft Releases 19 through 29. These issues primarily impacted on-premise installations and have been fully addressed in our most recent updates, specifically Releases 30 and 31.

We want to reassure you that all four issues required elevated access privileges to exploit. There is no evidence of malicious use in any customer environments. As soon as these issues were identified, we took immediate steps to correct them and strengthen our platform to help prevent similar risks in the future.

Below you’ll find a brief overview of each vulnerability, including which versions were affected and how the issue was resolved. If you're running an on-premise deployment, we strongly encourage you to upgrade to Release 31 to ensure any risk associated with these CVE’s is mitigated.

**CVE-2025-35113: Remote Code Execution via EUI Template Injection **

**Affected Versions**:** Agiloft Release 19 through Release 28 **

**Resolved In: Release 31**

 A critical vulnerability was found in the EUI template editor, which could allow users with administrative permissions to execute arbitrary system commands and Java code. This was possible through the Apache Velocity Engine and triggered when a malicious template was loaded. The code would execute each time a user viewed the page.

**Risk Context:** Only users with administrative access and permissions to import and edit EUI templates could potentially exploit this issue. Role-based access controls (RBAC) significantly limited exposure. We have no indication that this vulnerability was exploited in any customer environment.

**Mitigation:** This issue was fully resolved in Release 31, which includes safeguards that prevent unauthorized code execution through templates. We strongly recommend on-premise customers upgrade to this version.

**CVE-2025-35112: XML External Entity (XXE) Vulnerability in Import Functionality**

**Affected Versions: Agiloft Release 19 through Release 28**

**Resolved In: Release 31**

A vulnerability was identified in the XML import/export feature. Specially crafted XML files could be used to access restricted files on the server (such as /etc/passwd) through external entity references.

**Risk Context:**

Exploitation required access to the import feature, which is limited to administrative users through RBAC. This greatly reduced the risk of unauthorized access. We have found no evidence of this issue being used maliciously.

**Mitigation:**

This vulnerability was fully resolved in Release 31. We recommend all on-premise customers upgrade to this version.

**CVE-2025-35114: Default and Backdoor Credential Risk in On-Premise Installations **

**Affected Versions: Agiloft Release 19 through Release 29 **

**Resolved In: Release 30**

A vulnerability related to default and backdoor credentials was identified. Improper configuration during on-premise installation may result in user accounts being created with default credentials. If these credentials remain unchanged, an attacker could escalate privileges by leveraging them directly or by successfully performing offline brute-force attacks. This would effectively exploit a hidden backdoor authentication path.

**Risk Context:**

Improper configuration during on-premise installation may result in user accounts being created with default credentials. The risk was confined to environments where configuration instructions where not followed. Agiloft documentation on recommended secure configuration can be found at [https://wiki.agiloft.com/display/HELP/Password+Management](https://wiki.agiloft.com/display/HELP/Password+Management). There is no indication that these credentials were exploited in customer environments.

**Mitigation:**

As of Release 30, the creation of accounts with default or undocumented credentials is prevented through hardened account management. Users are strongly advised to follow Agiloft’s official on-premise installation guidance to ensure proper account configuration. On-premise customers should upgrade to Release 30 or later to fully eliminate this risk.

**CVE-2025-35115: Insecure Package Download in On-Premise Installations **

**Affected Versions: Agiloft Release 19 through Release 29**

**Resolved In: Release 30**

During on-premise installation our platform downloaded required packages via HTTP from a third-party domain ([database-download.com](http://database-download.com)). These packages were from unofficial sources and validated using MD5 checksums, which are not considered secure.

**Risk Context:**

 If the Agiloft installer was obtained from an unofficial source, or if installation was performed over an unsecured or untrusted network, there existed a window in which a malicious actor could have tampered with the downloaded components. Because the installer retrieved certain packages over HTTP and relied solely on MD5 checksums for validation, installations under these conditions were potentially susceptible to tampering or man-in-the-middle (MitM) attacks. We have seen no evidence of exploitation.

**Mitigation:**

Starting with Release 30, all required packages are downloaded over secure channels from verified sources, using modern integrity verification methods. This fully eliminates reliance on unverified third party sources and outdated hash algorithms. These changes were made to strengthen installation security and prevent any potential for supply chain tampering.