CVE-2024-5617

Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks

  • Medium 4.8

Description

The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account. This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.

Key facts

Published
2 Nov 2026
Last changed
2 Nov 2026
Assigned by
WSO2
EPSS
0.221% likely to be exploited in the next 30 days, higher than 12.731% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 4.8CVSS 3.1, Mediumfrom the CNA (WSO2)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

What to do

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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-210 CAPEC-210: Brute Force Attack (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
WSO2WSO2 API Manager
  • Default status: unaffected
  • 0 up to but excluding 4.0.0 (unknown)
  • 4.0.0 up to but excluding 4.0.0.298 (affected)
  • 4.2.0 up to but excluding 4.2.0.95 (affected)
  • 4.3.0 up to but excluding 4.3.0.13 (affected)
WSO2WSO2 Identity Server
  • Default status: unaffected
  • 0 up to but excluding 5.11.0 (unknown)
  • 5.11.0 up to but excluding 5.11.0.348 (affected)
  • 6.0.0 up to but excluding 6.0.0.194 (affected)
  • 6.1.0 up to but excluding 6.1.0.162 (affected)
  • 7.0.0 up to but excluding 7.0.0.33 (affected)
WSO2WSO2 Carbon Identity Management
  • Default status: unknown
  • 5.18.187 up to but excluding 5.18.187.259 (affected)
  • 5.23.8 up to but excluding 5.23.8.180 (affected)
  • 5.24.8 up to but excluding 5.24.8.5 (affected)
  • 5.25.92 up to but excluding 5.25.92.84 (affected)
  • 5.25.705 up to but excluding 5.25.705.5 (affected)
  • 7.0.78 up to but excluding 7.0.78.19 (affected)
WSO2WSO2 Carbon User Manager Kernel
  • Default status: unknown
  • 4.6.1 up to but excluding 4.6.1.114 (affected)
  • 4.7.1 up to but excluding 4.7.1.53 (affected)
  • 4.8.1 up to but excluding 4.8.1.16 (affected)
  • 4.9.0 up to but excluding 4.9.0.58 (affected)
  • 4.9.26 up to but excluding 4.9.26.7 (affected)
  • 4.10.9 up to but excluding 4.10.9.17 (affected)

Timeline

  1. 2 Nov 2026 Published

Weakness

References