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.
This vulnerability carries a CRITICAL severity rating with a CVSS v3.1 score of 9.8, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 9 products from wso2, from wso2, from wso2 and 6 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2025, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2025-11-18T15:16:38.530
2025-12-08T14:01:26.960
Analyzed
ed10eef1-636d-4fbe-9993-6890dfa878f8
CVSSv3.1: 9.8 (CRITICAL)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | wso2 | api_control_plane | 4.5.0 | Yes |
| Application | wso2 | api_manager | 2.2.0 | Yes |
| Application | wso2 | api_manager | 2.5.0 | Yes |
| Application | wso2 | api_manager | 2.6.0 | Yes |
| Application | wso2 | api_manager | 3.0.0 | Yes |
| Application | wso2 | api_manager | 3.1.0 | Yes |
| Application | wso2 | api_manager | 3.2.0 | Yes |
| Application | wso2 | api_manager | 3.2.1 | Yes |
| Application | wso2 | api_manager | 4.0.0 | Yes |
| Application | wso2 | api_manager | 4.1.0 | Yes |
| Application | wso2 | api_manager | 4.2.0 | Yes |
| Application | wso2 | api_manager | 4.3.0 | Yes |
| Application | wso2 | api_manager | 4.4.0 | Yes |
| Application | wso2 | api_manager | 4.5.0 | Yes |
| Application | wso2 | identity_server | 5.2.0 | Yes |
| Application | wso2 | identity_server | 5.3.0 | Yes |
| Application | wso2 | identity_server | 5.4.0 | Yes |
| Application | wso2 | identity_server | 5.4.1 | Yes |
| Application | wso2 | identity_server | 5.5.0 | Yes |
| Application | wso2 | identity_server | 5.6.0 | Yes |
| Application | wso2 | identity_server | 5.7.0 | Yes |
| Application | wso2 | identity_server | 5.8.0 | Yes |
| Application | wso2 | identity_server | 5.9.0 | Yes |
| Application | wso2 | identity_server | 5.10.0 | Yes |
| Application | wso2 | identity_server | 5.11.0 | Yes |
| Application | wso2 | identity_server | 6.0.0 | Yes |
| Application | wso2 | identity_server | 6.1.0 | Yes |
| Application | wso2 | identity_server | 7.0.0 | Yes |
| Application | wso2 | identity_server | 7.1.0 | Yes |
| Application | wso2 | identity_server | 7.2.0 | Yes |
| Application | wso2 | identity_server_as_key_manager | 5.3.0 | Yes |
| Application | wso2 | identity_server_as_key_manager | 5.5.0 | Yes |
| Application | wso2 | identity_server_as_key_manager | 5.6.0 | Yes |
| Application | wso2 | identity_server_as_key_manager | 5.7.0 | Yes |
| Application | wso2 | identity_server_as_key_manager | 5.9.0 | Yes |
| Application | wso2 | identity_server_as_key_manager | 5.10.0 | Yes |
| Application | wso2 | open_banking_am | 1.4.0 | Yes |
| Application | wso2 | open_banking_am | 1.5.0 | Yes |
| Application | wso2 | open_banking_am | 2.0.0 | Yes |
| Application | wso2 | open_banking_iam | 2.0.0 | Yes |
| Application | wso2 | open_banking_km | 1.4.0 | Yes |
| Application | wso2 | open_banking_km | 1.5.0 | Yes |
| Application | wso2 | traffic_manager | 4.5.0 | Yes |
| Application | wso2 | universal_gateway | 4.5.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For wso2's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.