A Cross-Site Request Forgery (CSRF) vulnerability exists in multiple WSO2 products due to the use of the HTTP GET method for state-changing operations within admin services, specifically in the event processor of the Carbon console. Although the SameSite=Lax cookie attribute is used as a mitigation, it is ineffective in this context because it allows cookies to be sent with cross-origin top-level navigations using GET requests. A malicious actor can exploit this vulnerability by tricking an authenticated user into visiting a crafted link, leading the browser to issue unintended state-changing requests. Successful exploitation could result in unauthorized operations such as data modification, account changes, or other administrative actions. According to WSO2 Secure Production Guidelines, exposure of Carbon console services to untrusted networks is discouraged, which may reduce the impact in properly secured deployments.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 8.8, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required 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-18T12:15:46.420
2025-12-08T14:00:21.493
Analyzed
ed10eef1-636d-4fbe-9993-6890dfa878f8
CVSSv3.1: 8.8 (HIGH)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | wso2 | api_control_plane | 4.5.0 | Yes |
| Application | wso2 | api_control_plane | 4.6.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 | api_manager | 4.6.0 | Yes |
| Application | wso2 | enterprise_integrator | 6.6.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.10.0 | Yes |
| Application | wso2 | open_banking_am | 2.0.0 | Yes |
| Application | wso2 | open_banking_iam | 2.0.0 | Yes |
| Application | wso2 | traffic_manager | 4.5.0 | Yes |
| Application | wso2 | traffic_manager | 4.6.0 | Yes |
| Application | wso2 | universal_gateway | 4.5.0 | Yes |
| Application | wso2 | universal_gateway | 4.6.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.