WSO2 API Manager: Improper Control of Generation of Code
CVE-2025-5717 is a high-severity improper control of generation of code vulnerability in WSO2 API Manager from WSO2, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 3.0.0.174, 3.1.0.330, 3.2.0.426 as the first without the flaw, so updating WSO2 API Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WSO2 API Manager to 3.0.0.174 or 3.1.0.330 or 3.2.0.426 or 3.2.1.46, whichever matches your release line, or a later version.
- Update WSO2 Open Banking AM to 2.0.0.379 or a later version.
- Update WSO2 Traffic Manager to 4.5.0.6 or a later version.
- Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WSO2 | WSO2 API Manager | 3.0.0 up to, but not including, 3.0.0.174; 3.1.0 up to, but not including, 3.1.0.330; 3.2.0 up to, but not including, 3.2.0.426; 3.2.1 up to, but not including, 3.2.1.46; 4.0.0 up to, but not including, 4.0.0.344; 4.1.0 up to, but not including, 4.1.0.208; 4.2.0 up to, but not including, 4.2.0.147; 4.3.0 up to, but not including, 4.3.0.59; and 2 more ranges | 3.0.0.174, 3.1.0.330, 3.2.0.426, 3.2.1.46, 4.0.0.344, 4.1.0.208 |
| WSO2 | WSO2 Open Banking AM | 2.0.0 up to, but not including, 2.0.0.379 | 2.0.0.379 |
| WSO2 | WSO2 Traffic Manager | 4.5.0 up to, but not including, 4.5.0.6 | 4.5.0.6 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.6 | 4.5.0.6 |
| WSO2 | Siddhi Extension Evaluate Scripts | 3.2.6 up to, but not including, 3.2.6.8; 3.2.7 up to, but not including, 3.2.7.6; 3.2.8 up to, but not including, 3.2.8.3; 3.2.10 up to, but not including, 3.2.10.1; 3.2.13 up to, but not including, 3.2.13.2; 3.2.14 up to, but not including, 3.2.14.1 | 3.2.6.8, 3.2.7.6, 3.2.8.3, 3.2.10.1, 3.2.13.2, 3.2.14.1 |
| WSO2 | API Control Plane | 4.5.0 | Not stated |
| 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 2 more ranges | Not stated |
| WSO2 | Open Banking Am | 2.0.0 | Not stated |
| WSO2 | Traffic Manager | 4.5.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.8 | Medium | CNA |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in WSO2 API Manager
- 9.8 Critical severity
- 8.7 High severity
- 9.4 Critical severity
- 8.3 High severity
- 9.1 Critical severity
- 8.4 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 9.8 Critical severity
- 10.0 Critical severity
- 8.8 High severity
- 9.0 Critical severity
- 8.8 High severity
- 10.0 Critical severity
Spotted an error? Tell us.