An incorrect authorization vulnerability exists in multiple WSO2 products due to a flaw in the SOAP admin service, which allows user account creation regardless of the self-registration configuration settings. This vulnerability enables malicious actors to create new user accounts without proper authorization. Exploitation of this flaw could allow an attacker to create multiple low-privileged user accounts, gaining unauthorized access to the system. Additionally, continuous exploitation could lead to system resource exhaustion through mass user creation.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 4.3, indicating it requires adjacent network access with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts limited integrity, for affected systems. Impacting 6 products from wso2, from wso2, from wso2 and 3 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-05-30T15:15:40.227
2025-10-06T13:51:05.690
Analyzed
ed10eef1-636d-4fbe-9993-6890dfa878f8
CVSSv3.1: 4.3 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | wso2 | api_manager | 2.1.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 | 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_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 | 2.0.0 | Yes |
| Application | wso2 | open_banking_iam | 2.0.0 | Yes |
| Application | wso2 | open_banking_km | 1.3.0 | Yes |
| Application | wso2 | open_banking_km | 1.4.0 | Yes |
| Application | wso2 | open_banking_km | 1.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.