CVE-2024-6832

Medium

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.

SeverityMedium
CVSS5.9
Exploit probability36. percentile0.4%
ProductWso2 Api Control Plane
PublishedAug 6, 2026
First seenAug 6, 2026
Weakness typeCWE-693CWE-693

How to fix

Affected products

ProductAffected versionsFixed in
wso2 api_control_plane4.5.0, 4.6.0—
wso2 api_manager3.1.0, 3.2.0, 3.2.1, 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0, 4.6.0—
wso2 identity_server5.10.0, 5.11.0, 6.0.0, 6.1.0, 7.0.0—
wso2 identity_server_as_key_manager5.10.0—
wso2 open_banking_am2.0.0—
wso2 open_banking_iam2.0.0—
wso2 traffic_manager4.5.0, 4.6.0—
wso2 universal_gateway4.5.0, 4.6.0—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.