WSO2 API Manager: Unrestricted Upload of File with Dangerous Type
CVE-2025-13590 is a high-severity unrestricted upload of file with dangerous type 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 4.2.0.179, 4.3.0.91, 4.4.0.55 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.77% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WSO2 API Manager to 4.2.0.179 or 4.3.0.91 or 4.4.0.55 or 4.5.0.38, whichever matches your release line, or a later version.
- Update WSO2 API Control Plane to 4.5.0.39 or 4.6.0.3, whichever matches your release line, or a later version.
- Update WSO2 Universal Gateway to 4.5.0.37 or 4.6.0.3, whichever matches your release line, 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 | 4.2.0 up to, but not including, 4.2.0.179; 4.3.0 up to, but not including, 4.3.0.91; 4.4.0 up to, but not including, 4.4.0.55; 4.5.0 up to, but not including, 4.5.0.38; 4.6.0 up to, but not including, 4.6.0.3 | 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.38, 4.6.0.3 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.39; 4.6.0 up to, but not including, 4.6.0.3 | 4.5.0.39, 4.6.0.3 |
| WSO2 | WSO2 Universal Gateway | 4.5.0 up to, but not including, 4.5.0.37; 4.6.0 up to, but not including, 4.6.0.3 | 4.5.0.37, 4.6.0.3 |
| WSO2 | WSO2 Traffic Manager | 4.5.0 up to, but not including, 4.5.0.37; 4.6.0 up to, but not including, 4.6.0.3 | 4.5.0.37, 4.6.0.3 |
| WSO2 | org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.impl | 9.28.116 up to, but not including, 9.28.116.391; 9.29.120 up to, but not including, 9.29.120.210; 9.30.67 up to, but not including, 9.30.67.133; 9.31.86 up to, but not including, 9.31.86.100; 9.32.147 up to, but not including, 9.32.147.2 | 9.28.116.391, 9.29.120.210, 9.30.67.133, 9.31.86.100, 9.32.147.2 |
| WSO2 | API Control Plane | 4.5.0; 4.6.0 | Not stated |
| WSO2 | API Manager | 4.2.0; 4.3.0; 4.4.0; 4.5.0; 4.6.0 | Not stated |
| WSO2 | Traffic Manager | 4.5.0; 4.6.0 | Not stated |
| WSO2 | Universal Gateway | 4.5.0; 4.6.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 | 9.1 | Critical | CNA |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
A malicious actor with administrative privileges can upload an arbitrary file to a user-controlled location within the deployment via a system REST API. Successful uploads may lead to remote code execution. By leveraging the vulnerability, a malicious actor may perform Remote Code Execution by uploading a specially crafted payload.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Unrestricted Upload of File with Dangerous Type
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
How developers prevent this class of flaw
- Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
More Unrestricted Upload of File with Dangerous Type vulnerabilities (CWE-434)
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 Unrestricted Upload of File with Dangerous Type vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.