Critical (10.0)

CVE-2025-12107: Due

CVE-2025-12107

Due to the use of a vulnerable third-party Velocity template engine, a malicious actor with admin privilege may inject and execute arbitrary template syntax within server-side templates. Successful...

Affected: Wso2 Identity Server

Overview

A critical security vulnerability exists in systems using a specific, vulnerable version of the Velocity template engine. This flaw allows an authenticated administrator to inject malicious code into server-side templates. If successfully exploited, an attacker could gain complete control over the affected server.

Vulnerability Details

This is a server-side template injection (SSTI) vulnerability. Templates are files used by applications to generate web pages or emails dynamically. The vulnerable template engine does not properly sanitize administrator input, allowing specially crafted template syntax to be executed directly on the server.

Key Point: Exploitation requires an attacker to first obtain administrative (“admin”) privileges within the application. This makes the vulnerability an escalation path, where a compromised admin account can lead to full server compromise.

Potential Impact

The consequences of this vulnerability are severe, earning it the maximum CVSS score of 10.0 (CRITICAL). A successful attack could lead to:

  • Remote Code Execution (RCE): An attacker could run any command or code on the underlying server operating system.
  • Data Manipulation or Theft: Sensitive data, including databases, user information, and system files, could be accessed, modified, or deleted.
  • Complete System Compromise: The attacker could establish persistent access, move to other systems on the network, or deploy ransomware.

Remediation and Mitigation

Immediate action is required to protect affected systems.

Primary Remediation:

  1. Upgrade the Template Engine: Identify all applications using the Velocity template engine. Consult your software vendor’s security advisory or the Velocity project’s documentation to determine the patched version. Upgrade the engine to this secure version immediately.
  2. Update Dependent Applications: Apply any available patches from your application vendors that address this specific CVE.

Mitigation Strategies (If Patching is Delayed):

  • Principle of Least Privilege: Rigorously review and minimize the number of administrator accounts. Ensure strong, unique passwords and multi-factor authentication (MFA) are enforced on all admin accounts to reduce the risk of them being compromised in the first place.
  • Network Segmentation: Isolate affected applications on their own network segments to limit the potential for lateral movement if the server is compromised.
  • Input Validation: While a full fix requires an engine update, review and harden any administrative interfaces that allow template editing or custom content injection.

Action Plan:

  1. Inventory your systems for use of the Velocity template engine.
  2. Apply the official patch or upgrade as a top priority.
  3. Audit administrator account activity and credentials.
  4. Monitor patched systems for any unusual activity.
Share:

Never miss a critical vulnerability

Get real-time security alerts delivered to your preferred platform.

Related Advisories

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.