The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.9, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), for affected systems. Impacting 8 products from wso2, from wso2, from wso2 and 5 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:27.533
2026-08-09T14:14:01.077
Analyzed
ed10eef1-636d-4fbe-9993-6890dfa878f8
CVSSv3.1: 5.9 (MEDIUM)
| 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.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 | 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.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.