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.

No CVSS v4.0

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact None

Availability Impact None

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
WSO2 WSO2 Enterprise Integrator unaffected
Version Status Constraints
0 unknown < 6.6.0
6.6.0 affected < 6.6.0.229
WSO2 WSO2 API Control Plane unaffected
Version Status Constraints
0 unknown < 4.5.0
4.5.0 affected < 4.5.0.40
4.6.0 affected < 4.6.0.4
4.6.0 affected < 4.6.0.5
WSO2 WSO2 Traffic Manager unaffected
Version Status Constraints
0 unknown < 4.5.0
4.5.0 affected < 4.5.0.38
4.6.0 affected < 4.6.0.4
4.6.0 affected < 4.6.0.5
WSO2 WSO2 Universal Gateway unaffected
Version Status Constraints
0 unknown < 4.5.0
4.5.0 affected < 4.5.0.38
4.6.0 affected < 4.6.0.4
4.6.0 affected < 4.6.0.5
WSO2 WSO2 API Manager unaffected
Version Status Constraints
0 unknown < 3.1.0
3.1.0 affected < 3.1.0.296
3.2.0 affected < 3.2.0.386
3.2.0 affected < 3.2.0.455
3.2.1 affected < 3.2.1.74
4.1.0 affected < 4.1.0.238
4.2.0 affected < 4.2.0.179
4.3.0 affected < 4.3.0.91
4.4.0 affected < 4.4.0.55
4.5.0 affected < 4.5.0.39
4.6.0 affected < 4.6.0.4
WSO2 WSO2 Identity Server unaffected
Version Status Constraints
0 unknown < 5.10.0
5.10.0 affected < 5.10.0.320
5.11.0 affected < 5.11.0.427
6.0.0 affected < 6.0.0.254
6.1.0 affected < 6.1.0.195
7.0.0 affected < 7.0.0.82
WSO2 WSO2 Identity Server as Key Manager unaffected
Version Status Constraints
0 unknown < 5.10.0
5.10.0 affected < 5.10.0.314
WSO2 WSO2 Open Banking IAM unaffected
Version Status Constraints
0 unknown < 2.0.0
2.0.0 affected < 2.0.0.366
WSO2 WSO2 Open Banking AM unaffected
Version Status Constraints
0 unknown < 2.0.0
2.0.0 affected < 2.0.0.345
WSO2 WSO2 Carbon User Manager Kernel unknown
Version Status Constraints
4.5.0 affected < 4.5.0.7
4.5.3 affected < 4.5.3.53
4.6.0 affected < 4.6.0.196
4.6.1 affected < 4.6.1.163
4.6.1 affected < 4.6.1.164
4.6.3 affected < 4.6.3.44
4.6.4 affected < 4.6.4.25
4.7.1 affected < 4.7.1.77
4.7.1 affected < 4.7.1.78
4.8.1 affected < 4.8.1.46
4.9.26 affected < 4.9.26.33
4.9.27 affected < 4.9.27.19
4.9.28 affected < 4.9.28.21
4.9.33 affected < 4.9.33.4
4.10.9 affected < 4.10.9.49
x unaffected ≤ *

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

No data.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/#solution

Workaround

No workaround given by the vendor.

References
Link Providers
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/ cve-icon
History

Thu, 06 Aug 2026 08:15:00 +0000

Type Values Removed Values Added
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.
Title Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks
Weaknesses CWE-693
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: WSO2

Published:

Updated: 2026-08-06T07:32:59.256Z

Reserved: 2024-07-17T11:44:02.821Z

Link: CVE-2024-6832

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-06T10:30:16Z

Weaknesses