Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-10908Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access

Description

Due to a lack of user account state validation during authentication, locked user accounts can be successfully authenticated using Magic Link or Pass Key methods. This bypasses the intended security control that should prevent access to accounts that have been locked. This vulnerability may allow unauthorized access to applications and sensitive data associated with accounts that should have been restricted via the account lock mechanism. It also undermines the effectiveness of the account lock mechanism intended to prevent further login attempts.

Timeline

  1. ID reserved

    By WSO2

  2. · 8 months later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-10908, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High7.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVDNVD · Analyzed3.1High7.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • WSO2 · WSO2 Identity Server

    • unknown < 6.0.0
    • affected 6.0.0 – < 6.0.0.249
    • affected 6.1.0 – < 6.1.0.248
    • affected 7.0.0 – < 7.0.0.124
    • affected 7.1.0 – < 7.1.0.31
  • WSO2 · WSO2 Carbon MagicLink Authenticator Module

    • affected 1.1.0 – < 1.1.0.1
    • affected 1.1.5 – < 1.1.5.2
    • affected 1.1.22 – < 1.1.22.5
    • affected 1.1.31 – < 1.1.31.2
    • unaffected 1.1.43 – ≤ *

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4388/#solution

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-10908 badge
[![CVE-2025-10908](https://cveledger.app/badge/CVE-2025-10908.svg)](https://cveledger.app/cve/CVE-2025-10908)

Record last updated .