Skip to main content
VulnerabilityPublished

CVE-2024-8122: WSO2 Identity Server · Insufficient Session Expiration

Affects WSO2 Identity ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium · fixed in 6.1.0.219 : update WSO2 Identity Server when convenient.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
5.9Medium
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.15.9
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.1.0.219, 6.0.0.227, 5.11.0.372
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 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 21 Nov 2026.

What to do

Upgrade WSO2 Identity Server and org.wso2.identity/wso2-identity-server to 6.1.0.219, 6.0.0.227 or 5.11.0.372.

Affected software

ProductAffectedFixed in
WSO2WSO2 Identity ServerAffected
  • >=6.1.0 <6.1.0.219
Fixed in
  • 6.1.0.219
WSO2WSO2 Identity ServerAffected
  • >=6.0.0 <6.0.0.227
Fixed in
  • 6.0.0.227
WSO2WSO2 Identity ServerAffected
  • >=5.11.0 <5.11.0.372
Fixed in
  • 5.11.0.372
Mavenorg.wso2.identity/wso2-identity-serverpkg:maven/org.wso2.identity/wso2-identity-serverOther threatsAffected
  • >=5.11.0 <5.11.0.372
  • >=6.0.0 <6.0.0.227
  • >=6.1.0 <6.1.0.219
Fixed in
  • 5.11.0.372
  • 6.0.0.227
  • 6.1.0.219

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

AI-suggested

If you cannot patch yet, organizations should consider additional compensating controls such as enforcing manual OTP expiration policies if configurable, monitoring for suspicious authentication attempts, or using alternative MFA methods with enforced expiration.

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.

References

Community reviews

Loading reviews…