CVE-2024-8122

Potential brute force vulnerability due to non-expiring SMS OTPs

  • Medium 5.9

Description

The WSO2 Identity Server fails to enforce a default expiry time for SMS One-Time Passwords (OTPs) used in multi-factor authentication (MFA). This allows unused OTPs to remain valid indefinitely, presenting an opportunity for malicious actors to conduct brute force attacks by repeatedly guessing the OTP. The absence of automatic expiration for OTPs grants attackers an unlimited timeframe to attempt guessing the correct code. A successful brute force attack can lead to an MFA bypass, resulting in the unauthorized takeover of a user's account and compromising the security and privacy of both the individual and the system.

Key facts

Published
8 Oct 2026
Last changed
8 Oct 2026
Assigned by
WSO2
EPSS
0.254% likely to be exploited in the next 30 days, higher than 17.055% of CVEs (scores for 17 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.

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

What to do

  • Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3149/#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-233 CAPEC-233: Brute Force (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 Identity Server
  • Default status: unaffected
  • 0 up to but excluding 5.11.0 (unknown)
  • 5.11.0 up to but excluding 5.11.0.372 (affected)
  • 6.0.0 up to but excluding 6.0.0.227 (affected)
  • 6.1.0 up to but excluding 6.1.0.219 (affected)

Timeline

  1. 8 Oct 2026 Published

Weakness

References