CVE-2025-70830 is a Server-Side Template Injection (SSTI) vulnerability affecting the Freemarker template engine integrated within Datart version 1.0.0-rc.3. SSTI vulnerabilities occur when user input is unsafely embedded in server-side templates, allowing attackers to inject and execute arbitrary code. In this case, authenticated attackers can inject crafted Freemarker template syntax into an SQL script field, which is then processed by the Freemarker engine. This injection enables execution of arbitrary code on the server hosting Datart, potentially leading to full system compromise. The vulnerability requires the attacker to be authenticated, which limits exploitation to users with some level of access, but does not require further user interaction. No patches or fixes have been publicly disclosed yet, and no known exploits are in the wild. The lack of a CVSS score indicates the vulnerability is newly published and not yet fully assessed, but the nature of SSTI and arbitrary code execution suggests a high risk. The vulnerability impacts the confidentiality, integrity, and availability of systems running the affected Datart version, as attackers could execute commands, access sensitive data, or disrupt services. The Freemarker template engine is widely used in Java-based applications, and Datart is a business intelligence platform that may be deployed in enterprise environments, increasing the potential impact.

For European organizations, this vulnerability poses a significant threat especially to those using Datart or similar BI tools that incorporate Freemarker templates. Successful exploitation can lead to unauthorized code execution, data breaches, and service disruptions. Confidential business intelligence data could be exposed or manipulated, undermining decision-making processes. The requirement for authentication reduces the attack surface but insider threats or compromised credentials could be leveraged by attackers. The impact extends to critical sectors such as finance, healthcare, and government agencies that rely on BI platforms for data analytics. Disruption or compromise of these systems could have cascading effects on operational continuity and regulatory compliance, including GDPR implications. Additionally, the lack of available patches means organizations must rely on mitigation strategies to reduce risk until a fix is released.

1. Restrict access to Datart instances strictly to trusted users and networks to minimize the risk of authenticated attackers. 2. Implement strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 3. Apply rigorous input validation and sanitization on all user inputs, especially those interacting with template engines or SQL fields, to prevent injection of malicious template syntax. 4. Monitor logs and application behavior for unusual template processing or execution patterns indicative of exploitation attempts. 5. Isolate the Datart environment using network segmentation and least privilege principles to limit potential damage from a successful attack. 6. Stay informed about vendor updates and apply patches promptly once available. 7. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SSTI payloads targeting Freemarker templates. 8. Conduct security reviews and code audits focusing on template usage and input handling within Datart deployments.