Cyber Resilience

CVE-2025-12107

Wso2 Identity Server 5.11.0

Published
19 February 2026
Modified
06 March 2026
Patch / advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0062 46th percentile
Risk Priority 56 floored blend · peak EPSS

Summary

CVE-2025-12107 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Wso2 Identity Server. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-12107 is a vulnerability stemming from the use of a vulnerable third-party Velocity template engine in WSO2 products. It enables a malicious actor with admin privileges to inject and execute arbitrary template syntax within server-side templates. Published on 2026-02-19, the issue is classified under CWE-1336 with a CVSS v3.1 base score of 8.4 (AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), indicating high severity due to its potential for significant impact across confidentiality, integrity, and availability in a changed scope.

Exploitation requires an attacker with high-privilege (admin) access on an adjacent network, achievable with low attack complexity and no user interaction. Upon successful injection of arbitrary template code, the attacker can achieve remote code execution on the server, data manipulation, or unauthorized access to sensitive information.

The WSO2 security advisory WSO2-2025-4517 provides details on mitigation and patches at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4517/.

EU & UK References

Vulnerability Data

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 exploitation of this vulnerability could allow a malicious actor with admin privilege…

more

to inject and execute arbitrary template code on the server, potentially leading to remote code execution, data manipulation, or unauthorized access to sensitive information.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-7487Same product: Wso2 Identity Server
CVE-2025-10470Same product: Wso2 Identity Server
CVE-2025-12624Same product: Wso2 Identity Server
CVE-2025-9973Same product: Wso2 Identity Server
CVE-2025-10908Same product: Wso2 Identity Server
CVE-2025-0209Same product: Wso2 Identity Server
CVE-2024-7103Same product: Wso2 Identity Server
CVE-2025-10503Same product: Wso2 Identity Server
CVE-2024-1524Same product: Wso2 Identity Server
CVE-2025-6024Same product: Wso2 Identity Server

Affected Assets

wso2
identity server
5.11.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2
  • V1.3.7
  • V1.3.10

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and static analysis can discover missing neutralization of template directives.

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

Security engineering principles require use of safe templating APIs and proper escaping of external input.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References