CyberSecBulletin
CVE-2025-9312NVD status: Analyzed

WSO2 API Manager: Missing Authentication for Critical Functionality

Published Updated By the CyberSecBulletin desk

CVE-2025-9312 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 2.2.0.58, 2.5.0.84, 2.6.0.145 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.25% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update WSO2 API Manager to 2.2.0.58 or 2.5.0.84 or 2.6.0.145 or 3.0.0.175, whichever matches your release line, or a later version.
  2. Update WSO2 API Control Plane to 4.5.0.22 or a later version.
  3. Update WSO2 Traffic Manager to 4.5.0.20 or a later version.
  4. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 API Manager2.2.0 up to, but not including, 2.2.0.58; 2.5.0 up to, but not including, 2.5.0.84; 2.6.0 up to, but not including, 2.6.0.145; 3.0.0 up to, but not including, 3.0.0.175; 3.1.0 up to, but not including, 3.1.0.339; 3.2.0 up to, but not including, 3.2.0.439; 3.2.1 up to, but not including, 3.2.1.59; 4.0.0 up to, but not including, 4.0.0.359; and 5 more ranges2.2.0.58, 2.5.0.84, 2.6.0.145, 3.0.0.175, 3.1.0.339, 3.2.0.439
WSO2WSO2 API Control Plane4.5.0 up to, but not including, 4.5.0.224.5.0.22
WSO2WSO2 Traffic Manager4.5.0 up to, but not including, 4.5.0.204.5.0.20
WSO2WSO2 Universal Gateway4.5.0 up to, but not including, 4.5.0.204.5.0.20
WSO2WSO2 Identity Server as Key Manager5.3.0 up to, but not including, 5.3.0.39; 5.5.0 up to, but not including, 5.5.0.52; 5.6.0 up to, but not including, 5.6.0.74; 5.7.0 up to, but not including, 5.7.0.124; 5.9.0 up to, but not including, 5.9.0.175; 5.10.0 up to, but not including, 5.10.0.3585.3.0.39, 5.5.0.52, 5.6.0.74, 5.7.0.124, 5.9.0.175, 5.10.0.358
WSO2WSO2 Identity Server5.2.0 up to, but not including, 5.2.0.33; 5.3.0 up to, but not including, 5.3.0.34; 5.4.0 up to, but not including, 5.4.0.33; 5.4.1 up to, but not including, 5.4.1.37; 5.5.0 up to, but not including, 5.5.0.51; 5.6.0 up to, but not including, 5.6.0.59; 5.7.0 up to, but not including, 5.7.0.125; 5.8.0 up to, but not including, 5.8.0.109; and 7 more ranges5.2.0.33, 5.3.0.34, 5.4.0.33, 5.4.1.37, 5.5.0.51, 5.6.0.59
WSO2WSO2 Open Banking KM1.4.0 up to, but not including, 1.4.0.132; 1.5.0 up to, but not including, 1.5.0.1221.4.0.132, 1.5.0.122
WSO2WSO2 Open Banking AM1.4.0 up to, but not including, 1.4.0.138; 1.5.0 up to, but not including, 1.5.0.139; 2.0.0 up to, but not including, 2.0.0.3881.4.0.138, 1.5.0.139, 2.0.0.388
WSO2WSO2 Open Banking IAM2.0.0 up to, but not including, 2.0.0.4082.0.0.408
WSO2org.wso2.carbon.identity.auth.service1.1.1 up to, but not including, 1.1.1.2; 1.1.16 up to, but not including, 1.1.16.3; 1.1.18 up to, but not including, 1.1.18.4; 1.1.20 up to, but not including, 1.1.20.5; 1.1.26 up to, but not including, 1.1.26.7; 1.3.6 up to, but not including, 1.3.6.8; 1.4.0 up to, but not including, 1.4.0.18; 1.4.25 up to, but not including, 1.4.25.24; and 7 more ranges1.1.1.2, 1.1.16.3, 1.1.18.4, 1.1.20.5, 1.1.26.7, 1.3.6.8
WSO2API Control Plane4.5.0Not stated
WSO2API Manager2.2.0; 2.5.0; 2.6.0; 3.0.0; 3.1.0; 3.2.0; 3.2.1; 4.0.0; and 5 more rangesNot stated
WSO2Identity Server5.2.0; 5.3.0; 5.4.0; 5.4.1; 5.5.0; 5.6.0; 5.7.0; 5.8.0; and 8 more rangesNot stated
WSO2Identity Server As Key Manager5.3.0; 5.5.0; 5.6.0; 5.7.0; 5.9.0; 5.10.0Not stated
WSO2Open Banking Am1.4.0; 1.5.0; 2.0.0Not stated
WSO2Open Banking Iam2.0.0Not stated
WSO2Open Banking Km1.4.0; 1.5.0Not stated
WSO2Traffic Manager4.5.0Not stated
WSO2Universal Gateway4.5.0Not 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

A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default configurations, the affected components may permit unauthenticated requests even when mTLS is enabled. This condition occurs when relying on the default mTLS settings for System REST APIs or when the mTLS authenticator is enabled for SOAP services, causing these interfaces to accept requests without enforcing additional authentication. Successful exploitation allows a malicious actor with network access to the affected endpoints to gain administrative privileges and perform unauthorized operations. The vulnerability is exploitable only when the impacted mTLS flows are enabled and accessible in a given deployment. Other certificate-based authentication mechanisms such as Mutual TLS OAuth client authentication and X.509 login flows are not affected, and APIs served through the API Gateway of WSO2 API Manager remain unaffected.

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

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in WSO2 API Manager

All WSO2 API Manager vulnerabilities

Recent Missing Authentication for Critical Functionality vulnerabilities

Spotted an error? Tell us.