The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-Site Request Forgery (CSRF) attacks. Specifically, it utilizes the HTTP GET method for these operations, and while the SameSite=Lax cookie attribute is employed for mitigation, this mechanism is bypassed as it permits cookies to be sent with cross-origin top-level navigation requests, including GET requests. This allows an attacker to trick an authenticated user's browser into unknowingly executing unintended actions. An attacker can exploit this vulnerability to perform unauthorized state-altering requests on behalf of authenticated users. This could lead to consequences such as data modification, account changes, or other actions that could result in data compromise or loss of user control over their account. However, this attack is only feasible if the Carbon console and related services are exposed to the public internet, which is not recommended according to WSO2's security guidelines.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.4, 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 limited integrity, and limited availability 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 2026, 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.
2026-08-06T08:16:28.210
2026-09-29T14:10:00.117
Analyzed
ed10eef1-636d-4fbe-9993-6890dfa878f8
CVSSv3.1: 5.4 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | wso2 | api_control_plane | < 4.5.0.39 | Yes |
| Application | wso2 | api_control_plane | < 4.6.0.3 | Yes |
| Application | wso2 | api_manager | < 3.1.0.352 | Yes |
| Application | wso2 | api_manager | < 3.2.0.456 | Yes |
| Application | wso2 | api_manager | < 3.2.1.75 | Yes |
| Application | wso2 | api_manager | < 4.0.0.376 | Yes |
| Application | wso2 | api_manager | < 4.1.0.239 | Yes |
| Application | wso2 | api_manager | < 4.2.0.179 | Yes |
| Application | wso2 | api_manager | < 4.3.0.91 | Yes |
| Application | wso2 | api_manager | < 4.4.0.55 | Yes |
| Application | wso2 | api_manager | < 4.5.0.38 | Yes |
| Application | wso2 | api_manager | < 4.6.0.3 | Yes |
| Application | wso2 | enterprise_integrator | < 6.6.0.227 | Yes |
| Application | wso2 | identity_server | < 5.10.0.381 | Yes |
| Application | wso2 | identity_server | < 5.11.0.428 | Yes |
| Application | wso2 | identity_server | < 6.0.0.255 | Yes |
| Application | wso2 | identity_server | < 6.1.0.256 | Yes |
| Application | wso2 | identity_server | < 7.0.0.133 | Yes |
| Application | wso2 | identity_server | < 7.1.0.41 | Yes |
| Application | wso2 | identity_server | < 7.2.0.3 | Yes |
| Application | wso2 | identity_server_as_key_manager | < 5.10.0.372 | Yes |
| Application | wso2 | open_banking_am | < 2.0.0.401 | Yes |
| Application | wso2 | open_banking_iam | < 2.0.0.421 | Yes |
| Application | wso2 | traffic_manager | < 4.5.0.37 | Yes |
| Application | wso2 | traffic_manager | < 4.6.0.3 | Yes |
| Application | wso2 | universal_gateway | < 4.5.0.37 | Yes |
| Application | wso2 | universal_gateway | < 4.6.0.3 | 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.