CVE-2024-7478Medium· 5.8▾ SunlitWhen a WSO2 product is configured to use an external user store, the system fails to adequately obscure the existence or validity of usernames during authentication attempts. This oversight allows an attacker to repeatedly query the auth…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 31.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
When a WSO2 product is configured to use an external user store, the system fails to adequately obscure the existence or validity of usernames during authentication attempts. This oversight allows an attacker to repeatedly query the authentication mechanism with different username guesses, enabling the enumeration of valid usernames present in the external user store.
The discovery of valid usernames can increase the risk of targeted brute-force attacks, social engineering, and information leakage. Attackers can leverage this information to craft more convincing phishing campaigns or other social engineering tactics to trick users into revealing sensitive data. The presence of username enumeration could also negatively impact an organization's reputation, leading to loss of customer trust, regulatory non-compliance, and potential legal and financial repercussions.
api_manager >= 3.1.0 < 3.1.0.310api_manager >= 3.2.0 < 3.2.0.401api_manager >= 3.2.1 < 3.2.1.26api_manager >= 4.0.0 < 4.0.0.318api_manager >= 4.1.0 < 4.1.0.180api_manager >= 4.2.0 < 4.2.0.119api_manager >= 4.3.0 < 4.3.0.30identity_server_as_key_manager >= 5.10.0 < 5.10.0.320identity_server >= 5.10.0 < 5.10.0.326identity_server >= 6.0.0 < 6.0.0.214identity_server >= 6.1.0 < 6.1.0.198identity_server >= 7.0.0 < 7.0.0.67open_banking_iam >= 2.0.0 < 2.0.0.371open_banking_am >= 2.0.0 < 2.0.0.351org.wso2.carbon.identity.handler.event.account.lock >= 1.4.0 < 1.4.0.15org.wso2.carbon.identity.handler.event.account.lock >= 1.4.0 < 1.4.0.16org.wso2.carbon.identity.handler.event.account.lock >= 1.4.11 < 1.4.11.14org.wso2.carbon.identity.handler.event.account.lock >= 1.4.37 < 1.4.37.1org.wso2.carbon.identity.handler.event.account.lock >= 1.6.1 < 1.6.1.5org.wso2.carbon.identity.handler.event.account.lock >= 1.7.1 < 1.7.1.1org.wso2.carbon.identity.handler.event.account.lock >= 1.8.6 < 1.8.6.5org.wso2.carbon.identity.handler.event.account.lock >= 1.8.14 < 1.8.14.1org.wso2.carbon.identity.handler.event.account.lock >= 1.9.2 < 1.9.2.4Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3606/#solution
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-6423Medium· 4.0Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage
CVE-2024-4989Medium· 5.4Open Redirection via Callback URL in WSO2 API Manager Allows Phishing Attacks
CVE-2025-7043Medium· 5.4Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption
CVE-2025-6623Medium· 4.3Stored Cross-Site Scripting via XML Input in Multiple WSO2 Products Allows UI Manipulation and Redirection
CVE-2025-13590Critical· 9.1Authenticated arbitrary file upload via a System REST API requiring administrator permission.
CVE-2026-3418Critical· 9.1Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution