WSO2 API Manager
CVE-2025-5717
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain WSO2 admin credentials
-
DeliveryAuthenticate to SOAP admin services
-
ExploitDeploy malicious Siddhi execution plan
-
ExecutionEmbedded Java executes on server
-
ImpactArbitrary code execution as service account
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid account with administrative access to the WSO2 SOAP admin services, specifically the ability to reach the event processor admin service and deploy a Siddhi execution plan. The concrete prerequisite is permission to author/deploy Siddhi plans, which accept Java that is executed without adequate input validation. Limiting factors: PR:H (administrative authentication is mandatory, not obtainable anonymously), no user interaction needed once authenticated, and exposure is further reduced if the SOAP/admin management console is network-restricted or not internet-facing. There is no unauthenticated path in the provided data. |
| Impact | This is a post-authentication RCE (CWE-94) requiring high privileges, and the signals converge on moderate rather than critical real-world urgency. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) confirms network reach and full CIA impact but gates exploitation behind PR:H - an administrator of the SOAP admin services. EPSS is low at 0.33% (56th percentile), consistent with a vulnerability that is not being broadly scanned or mass-exploited. The CVE is NOT in CISA KEV and no public exploit was provided in the input (no public exploit identified at time of analysis). No SSVC decision data was supplied. These signals are mutually consistent: a genuine RCE, but one whose precondition (administrative access to admin services) sharply narrows the realistic attacker population to insiders, compromised-admin, or credential-theft scenarios. Treat it as a privilege-escalation-to-code-execution / defense-in-depth concern rather than an internet-facing emergency - the main driver is that an admin-level foothold on WSO2 converts directly into OS-level code execution, collapsing any trust boundary between app-admin and the host. |
| Exploit ScenarioDerived | An attacker who has obtained WSO2 administrator credentials (e.g., via phishing, credential reuse, or a malicious insider) authenticates to the SOAP admin services and uses the event processor admin service to deploy a Siddhi execution plan embedding malicious Java. When the plan is processed the embedded code executes with the privileges of the WSO2 service account, giving the attacker arbitrary code execution on the server. No public exploit was identified in the provided data, and success depends on already holding administrative access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 18, 2026
Administrative users of WSO2 API Manager (3.0.0 through 4.4.0) and related WSO2 components such as API Control Plane 4.5.0 can achieve arbitrary code execution on the server by deploying a crafted Siddhi execution plan through the event processor admin service, which fails to validate embedded Java code. Because the flaw is reachable only over the SOAP admin services with high-privilege credentials (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2), it is a post-authentication escalation path for a trusted-but-malicious or compromised administrator rather than an anonymous attack vector; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and EPSS is low at 0.33% (56th percentile).
Earlier versions of this analysis (1)
An authenticated remote code execution (RCE) vulnerability exists in multiple WSO2 products due to improper input validation in the event processor admin service. Rated medium severity (CVSS 6.8), this vulnerability is low attack complexity. No vendor patch available.
RemediationAI
Apply the security updates published in WSO2 advisory WSO2-2025-4119 (https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4119/) for each affected product line - API Manager 3.x/4.x, API Control Plane 4.5.0, Open Banking AM and Traffic Manager - following WSO2's update-tool or public-patch instructions; the advisory is the source of truth for exact patched builds and should be consulted because specific fix version numbers are not included in the data provided here. Until patched, reduce the attack surface by removing or disabling the event processor admin service if event processing is not in use (this disables Siddhi-based CEP functionality), and block external access to the /services/* SOAP admin endpoints and the management console at the reverse proxy or firewall so only trusted administration networks can reach them (management must then be performed from a bastion or VPN). Additionally, audit and remove unnecessary administrative accounts and any unknown Siddhi execution plans, enforce least-privilege role assignment so plan deployment is limited to a small vetted group, rotate credentials for accounts with admin-service access in case of prior compromise, and run WSO2 with a non-root service account plus restrictive outbound egress to limit post-exploitation impact - noting that network restriction and service removal mitigate but do not remediate the underlying improper input validation.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WSO2 middleware exposes a family of SOAP-based admin services used for management operations, including an event processor admin service that manages Siddhi execution plans. Siddhi is WSO2's complex-event-processing / streaming query engine, and execution plans are authored artifacts that may embed Java logic executed by the server at runtime. The vulnerability is CWE-94 (Improper Control of Generation of Code / Code Injection): the service accepts a plan without adequately validating or sandboxing the Java content it carries, so a plan author can have arbitrary code run in the WSO2 process context. The CVSS vector confirms network reachability with low attack complexity and no user interaction, but PR:H reflects that the attacker must already hold an administrative account able to invoke the admin services and deploy plans. CPE data enumerates WSO2 API Manager 3.0.0, 3.1.0, 3.2.0, 3.2.1, 4.0.0, 4.1.0, 4.2.0, 4.3.0 and 4.4.0 alongside API Control Plane 4.5.0; vendor tagging also associates the defect with the Open Banking AM and Traffic Manager product lines, which share the same underlying admin-service and event-processing stack.
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Network-reachable admin service with no user interaction (AV:N/AC:L/UI:N), but deploying Siddhi plans requires administrative privileges (PR:H); embedded Java yields full host code execution (C/I/A:H), scope unchanged.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
An authenticated remote code execution (RCE) vulnerability exists in multiple WSO2 products due to improper input validation in the event processor admin service. A user with administrative access to the SOAP admin services can exploit this flaw by deploying a Siddhi execution plan containing malicious Java code, resulting in arbitrary code execution on the server.
Exploitation of this vulnerability requires a valid user account with administrative privileges, limiting the attack surface to authenticated but potentially malicious users.
Executive ViewAI
WSO2 API Manager versions 3.0.0 through 4.4.0, along with API Control Plane 4.5.0, contain a high-severity flaw that lets a privileged administrator execute arbitrary code on the server via the event processor admin service. Because no vendor patch is currently available and the attack path requires high-privilege credentials, leadership should treat this as an insider-risk and compromised-admin-account exposure affecting the integrity and availability of API gateway infrastructure. The low EPSS score and absence of public exploit code reduce urgency but do not eliminate the need to harden administrative access and monitor for misuse.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting SOAP administrative service access to trusted networks, enforcing MFA and least privilege for administrator accounts, disabling the event processor admin service if unused, auditing Siddhi execution plan deployments, and monitoring administrative activity for anomalous code execution attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)NVD
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB