CVE-2025-0672
BaseFortify
Publication date: 2025-09-23
Last updated on: 2025-10-03
Assigner: WSO2 LLC
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wso2 | identity_server | 5.10.0 |
| wso2 | identity_server | 5.11.0 |
| wso2 | identity_server_as_key_manager | 5.10.0 |
| wso2 | open_banking_iam | 2.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an authentication bypass issue in multiple WSO2 products when FIDO authentication is enabled. When a user account is deleted, the system does not remove the associated FIDO registration data. If a new user account is created later with the same username, the system may link the new account to the old FIDO device, allowing the previously deleted user to authenticate and impersonate the new user.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized access by enabling a previously deleted user to authenticate using their old FIDO credentials and impersonate a newly created user with the same username. This could lead to unauthorized access to the new user's account and potentially sensitive information.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that when a user account is deleted, all associated FIDO registration data is also removed to prevent reuse of FIDO credentials by a new user with the same username. Additionally, review and restrict FIDO-based authentication usage and monitor user account deletions to verify proper cleanup of authentication data.