CVE-2024-6832: The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not…
CVE-2024-6832 · Severity: medium · CVSS 5.9 · Published 2026-08-06
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. Junglewise Threat Intelligence has no report of CVE-2024-6832 being exploited in the wild.
How severe is CVE-2024-6832?
Medium severity, with a CVSS score of 5.9, published 6 August 2026.
Which products and versions are affected?
Wso2 API Control Plane, Wso2 API Manager, Wso2 Identity Server, Wso2 Identity Server as Key Manager and 4 more. The advisory does not name versions.
Is there a fix for CVE-2024-6832?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2024-6832?
Check whether you run Wso2 API Control Plane, Wso2 API Manager, Wso2 Identity Server or one of the others listed. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.