WSO2 API Manager: Improper Privilege Management
CVE-2026-1728 is a critical-severity improper privilege management vulnerability in WSO2 API Manager from WSO2, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.0.0.384, 4.1.0.248, 4.2.0.188 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.48% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update WSO2 API Manager to 4.0.0.384 or 4.1.0.248 or 4.2.0.188 or 4.3.0.99, whichever matches your release line, or a later version.
- Update WSO2 API Control Plane to 4.5.0.49 or 4.6.0.13, whichever matches your release line, or a later version.
- Update WSO2 Universal Gateway to 4.5.0.48 or 4.6.0.12, whichever matches your release line, or a later version.
- Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WSO2 | WSO2 API Manager | 4.0.0 up to, but not including, 4.0.0.384; 4.1.0 up to, but not including, 4.1.0.248; 4.2.0 up to, but not including, 4.2.0.188; 4.3.0 up to, but not including, 4.3.0.99; 4.4.0 up to, but not including, 4.4.0.63; 4.5.0 up to, but not including, 4.5.0.48; 4.6.0 up to, but not including, 4.6.0.12 | 4.0.0.384, 4.1.0.248, 4.2.0.188, 4.3.0.99, 4.4.0.63, 4.5.0.48 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.49; 4.6.0 up to, but not including, 4.6.0.13 | 4.5.0.49, 4.6.0.13 |
| WSO2 | WSO2 Universal Gateway | 4.5.0 up to, but not including, 4.5.0.48; 4.6.0 up to, but not including, 4.6.0.12 | 4.5.0.48, 4.6.0.12 |
| WSO2 | WSO2 Traffic Manager | 4.5.0 up to, but not including, 4.5.0.47; 4.6.0 up to, but not including, 4.6.0.12 | 4.5.0.47, 4.6.0.12 |
| WSO2 | WSO2 Carbon API Manager Rest API Common Functions | 9.0.174 up to, but not including, 9.0.174.550; 9.28.116 up to, but not including, 9.28.116.404; 9.29.120 up to, but not including, 9.29.120.221; 9.30.67 up to, but not including, 9.30.67.146; 9.31.86 up to, but not including, 9.31.86.130; 9.32.147 up to, but not including, 9.32.147.26 | 9.0.174.550, 9.28.116.404, 9.29.120.221, 9.30.67.146, 9.31.86.130, 9.32.147.26 |
| WSO2 | WSO2 Carbon API Manager Rest API Utility | 9.20.74 up to, but not including, 9.20.74.392 | 9.20.74.392 |
| WSO2 | API Control Plane | 4.5.0 up to, but not including, 4.5.0.49; 4.6.0 up to, but not including, 4.6.0.13 | 4.5.0.49, 4.6.0.13 |
| WSO2 | API Manager | 4.0.0 up to, but not including, 4.0.0.384; 4.1.0 up to, but not including, 4.1.0.248; 4.2.0 up to, but not including, 4.2.0.188; 4.3.0 up to, but not including, 4.3.0.99; 4.4.0 up to, but not including, 4.4.0.63; 4.5.0 up to, but not including, 4.5.0.48; 4.6.0 up to, but not including, 4.6.0.12 | 4.0.0.384, 4.1.0.248, 4.2.0.188, 4.3.0.99, 4.4.0.63, 4.5.0.48 |
| WSO2 | Traffic Manager | 4.5.0 up to, but not including, 4.5.0.47; 4.6.0 up to, but not including, 4.6.0.12 | 4.5.0.47, 4.6.0.12 |
| WSO2 | Universal Gateway | 4.5.0 up to, but not including, 4.5.0.48; 4.6.0 up to, but not including, 4.6.0.12 | 4.5.0.48, 4.6.0.12 |
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
- NoneNo account or login is needed.
- 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:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs. Exploitation of this vulnerability allows a low-privileged user to invoke the Admin REST APIs of WSO2 products, potentially leading to full administrative account takeover. This requires the attacker to already possess a low-privileged user account and be able to obtain a valid token for it.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, 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 Privilege Management vulnerabilities
- 9.9 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
- 8.1 High severity
- 8.8 High severity
Spotted an error? Tell us.