CVE-2025-10908
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDue 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe authentication system fails to validate user account lock state when processing Magic Link and Pass Key authentication methods. When a user account has been locked (either manually by admins or automatically after failed attempts), the account state check is bypassed during these alternative authentication flows, allowing the locked account to successfully authenticate.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 6.0.0, < 6.0.0.249>= 6.1.0, < 6.1.0.248>= 7.0.0, < 7.0.0.124>= 7.1.0, < 7.1.0.31CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WSO2 Identity Server installed versionCheck the product version from the management console or the <PRODUCT_HOME>/repository/components/WSO2-Product-Version.properties file. Common paths: wso2is/bin/wso2server.sh --version or the carbon console about page.Affected if Installed version falls within any of these ranges: >= 6.0.0 and < 6.0.0.249; >= 6.1.0 and < 6.1.0.248; >= 7.0.0 and < 7.0.0.124; >= 7.1.0 and < 7.1.0.31
-
Verify if Magic Link authentication is enabledCheck the authentication configurations in the WSO2 Identity Server management console under Login > Authentication Gates or review the application-authentication.xml file in the repository/conf/identity directory for Magic Link connector enablement.Affected if Magic Link authentication method is enabled for any application or as a secondary authentication option in your environment
-
Verify if Pass Key authentication is enabledCheck the authentication configurations in the WSO2 Identity Server management console under Login > Authentication Gates or review the application-authentication.xml file for Passkey (FIDO) connector enablement.Affected if Pass Key (FIDO2/WebAuthn) authentication method is enabled for any application or as a secondary authentication option in your environment
-
Confirm account lock functionality is in useReview the account lock settings in the WSO2 Identity Server management console under Identity Providers > User Management > Account Lock or check the identity-mgt.properties file for account.lock.enabled configuration.Affected if Account locking is enabled (either manual admin lock or automatic lock after failed attempts) in your identity server configuration
You are affected if your WSO2 Identity Server version falls within the affected ranges AND you have either Magic Link or Pass Key authentication enabled, while also using the account lock feature - the locked account check will be bypassed during those alternative authentication flows.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.0.0.2496.1.0.2487.0.0.124
Implement mandatory account state validation (including locked status check) in all authentication pathways, ensuring locked accounts cannot complete authentication regardless of the method used (password, Magic Link, or Pass Key).
Upgrade to WSO2 Identity Server 6.0.0.249 (for 6.0.x), 6.1.0.248 (for 6.1.x), 7.0.0.124 (for 7.0.x), or 7.1.0.31 (for 7.1.x)
- 1. Identify the currently running WSO2 Identity Server version from the affected list (6.0.0.x, 6.1.0.x, 7.0.0.x, or 7.1.0.x)
- 2. Create a full backup of the current Identity Server deployment including configuration files, databases, and deployment directory
- 3. Download the appropriate fixed version from the WSO2 official distribution repository: 6.0.0.249, 6.1.0.248, 7.0.0.124, or 7.1.0.31
- 4. Set up a staging environment identical to production and apply the fixed version
- 5. Migrate configurations and user data to the staging environment following WSO2 migration documentation
- 6. Test authentication flows including Magic Link and Pass Key methods with locked accounts to verify the fix
- 7. Schedule a maintenance window and deploy the fixed version to production
- 8. Monitor authentication logs to confirm that locked accounts are properly rejected for all authentication methods
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10908 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data