CVE-2024-6832
published 2026-08-06CVE-2024-6832: The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account…
PriorityP348high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
0.41%
34.1th percentile
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.
Affected
66 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| wso2 | api_control_plane | — | — |
| wso2 | api_control_plane | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | api_manager | — | — |
| wso2 | identity_server | — | — |
| wso2 | identity_server | — | — |
| wso2 | identity_server | — | — |
| wso2 | identity_server | — | — |
| wso2 | identity_server | — | — |
| wso2 | identity_server_as_key_manager | — | — |
| wso2 | open_banking_am | — | — |
| wso2 | open_banking_iam | — | — |
| wso2 | traffic_manager | — | — |
| wso2 | traffic_manager | — | — |
| wso2 | universal_gateway | — | — |
| wso2 | universal_gateway | — | — |
| wso2 | wso2_api_control_plane | >= 4.5.0 < 4.5.0.40 | 4.5.0.40 |
| wso2 | wso2_api_control_plane | >= 4.6.0 < 4.6.0.4 | 4.6.0.4 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
WSO2 API Control Plane Account Locking Mechanism locking
vuldb·2026-08-10·CVSS 7.5
CVE-2024-6832 [HIGH] WSO2 API Control Plane Account Locking Mechanism locking
A vulnerability categorized as very critical has been discovered in WSO2 API Control Plane, API Manager, Carbon User Manager Kernel, Enterprise Integrator, Identity Server, Identity Server as Key Manager, Open Banking AM, Open Banking IAM, Traffic Manager and Universal Gateway. This affects an unknown part of the component Account Locking Mechanism. The manipulation results in improper locking.
This vulnerability is known as CVE-2024-6832. It is possible to launch the attack remotely. No exploit is available.
GHSA
The account locking mechanism fails to trigger when secondary user stores are inaccessible.
ghsa_unreviewed·2026-08-06
CVE-2024-6832 [MEDIUM] CWE-693 The account locking mechanism fails to trigger when secondary user stores are inaccessible.
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 detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-08-06
Published