WSO2 API Manager: Missing Authentication for Critical Functionality
CVE-2025-9152 is a critical-severity missing authentication for critical functionality 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 3.2.0.437, 3.2.1.57, 4.0.0.357 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.71% chance of exploitation within 30 days, higher than 54% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update WSO2 API Manager to 3.2.0.437 or 3.2.1.57 or 4.0.0.357 or 4.1.0.221, whichever matches your release line, or a later version.
- Update WSO2 API Control Plane to 4.5.0.20 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 | 3.2.0 up to, but not including, 3.2.0.437; 3.2.1 up to, but not including, 3.2.1.57; 4.0.0 up to, but not including, 4.0.0.357; 4.1.0 up to, but not including, 4.1.0.221; 4.2.0 up to, but not including, 4.2.0.159; 4.3.0 up to, but not including, 4.3.0.72; 4.4.0 up to, but not including, 4.4.0.35; 4.5.0 up to, but not including, 4.5.0.19 | 3.2.0.437, 3.2.1.57, 4.0.0.357, 4.1.0.221, 4.2.0.159, 4.3.0.72 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.20 | 4.5.0.20 |
| WSO2 | API Control Plane | 4.5.0 | Not stated |
| WSO2 | API Manager | 3.2.0; 3.2.1; 4.0.0; 4.1.0; 4.2.0; 4.3.0; 4.4.0; 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
- 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
An improper privilege management vulnerability exists in WSO2 API Manager due to missing authentication and authorization checks in the keymanager-operations Dynamic Client Registration (DCR) endpoint. A malicious user can exploit this flaw to generate access tokens with elevated privileges, potentially leading to administrative access and the ability to perform unauthorized operations.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
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 Missing Authentication for Critical Functionality vulnerabilities
- 8.4 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.