CVE-2024-5617Medium· 4.8▾ SunlitThe account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 26.4 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account.
This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.
api_manager >= 4.0.0 < 4.0.0.298api_manager >= 4.2.0 < 4.2.0.95api_manager >= 4.3.0 < 4.3.0.13identity_server >= 5.11.0 < 5.11.0.348identity_server >= 6.0.0 < 6.0.0.194identity_server >= 6.1.0 < 6.1.0.162identity_server >= 7.0.0 < 7.0.0.33org.wso2.carbon.identity.mgt >= 5.18.187 < 5.18.187.259org.wso2.carbon.identity.mgt >= 5.23.8 < 5.23.8.180org.wso2.carbon.identity.mgt >= 5.24.8 < 5.24.8.5org.wso2.carbon.identity.mgt >= 5.25.92 < 5.25.92.84org.wso2.carbon.identity.mgt >= 5.25.705 < 5.25.705.5org.wso2.carbon.identity.mgt >= 7.0.78 < 7.0.78.19org.wso2.carbon:org.wso2.carbon.user.core >= 4.6.1 < 4.6.1.114org.wso2.carbon:org.wso2.carbon.user.core >= 4.7.1 < 4.7.1.53org.wso2.carbon:org.wso2.carbon.user.core >= 4.8.1 < 4.8.1.16org.wso2.carbon:org.wso2.carbon.user.core >= 4.9.0 < 4.9.0.58org.wso2.carbon:org.wso2.carbon.user.core >= 4.9.26 < 4.9.26.7org.wso2.carbon:org.wso2.carbon.user.core >= 4.10.9 < 4.10.9.17Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/#solution
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-0637Medium· 5.4Header Injection via Custom URL Configuration in Multiple WSO2 Products Allows Open Redirect and Log Forgery
CVE-2026-4052Critical· 9.8Privilege Escalation via Token Endpoint in WSO2 API Manager (APIM 4.x/IS as Resident Key Manager)
CVE-2025-11969Critical· 9.4Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized Administrative Actions
CVE-2024-12139Medium· 4.3Content Spoofing via Error Handling in Multiple WSO2 Products Enables Social Engineering Attacks
CVE-2026-18800Medium· 4.4Information Disclosure via Event Publisher Logging in Multiple WSO2 Products Allows Retrieval of Sensitive Data
CVE-2026-2613High· 8.7SQL Injection via Admin REST API in Multiple WSO2 Products Allows Database Information Inference and Service Disruption