Skip to main content
VulnerabilityPublished

CVE-2024-5617: WSO2 API Manager · Improper Control of Interaction Frequency

Affects WSO2 API ManagerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium · fixed in 4.3.0.13 : update WSO2 API Manager when convenient.

Data as of 2 Nov 2026, 06:43 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (WSO2)CVSS 3.14.8
Patch
Available – fixed in 4.3.0.13, 4.2.0.95, 4.0.0.298 +16
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
WSO2WSO2 API ManagerAffected
  • >=4.3.0 <4.3.0.13
Fixed in
  • 4.3.0.13
WSO2WSO2 API ManagerAffected
  • >=4.2.0 <4.2.0.95
Fixed in
  • 4.2.0.95
WSO2WSO2 API ManagerAffected
  • >=4.0.0 <4.0.0.298
Fixed in
  • 4.0.0.298
WSO2WSO2 Identity ServerAffected
  • >=7.0.0 <7.0.0.33
Fixed in
  • 7.0.0.33
WSO2WSO2 Identity ServerAffected
  • >=6.1.0 <6.1.0.162
Fixed in
  • 6.1.0.162
WSO2WSO2 Identity ServerAffected
  • >=6.0.0 <6.0.0.194
Fixed in
  • 6.0.0.194

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Fixed versions are available for this vulnerability. Users should upgrade to one of the fixed releases: 4.0.0.298, 4.2.0.95, 4.3.0.13, 5.11.0.348, 6.0.0.194, 6.1.0.162, 7.0.0.33, 7.0.78.19, 5.25.705.5, or 5.25.92.84. Applying these official fixes will remediate the issue. No additional mitigation is required if upgraded.

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.

References

Community reviews

Loading reviews…