{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-0672 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0672 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0672 is a low-severity authentication bypass vulnerability in Wso2 Identity Server, published on 23 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0672 and fix it if it is affected.\n\nWhat it is: CVE-2025-0672 is a low-severity authentication bypass vulnerability in Wso2 Identity Server, published on 23 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-0672 in the wild and no public exploit code.\n\nAffected product: Wso2 Identity Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-0672/ (Markdown: https://insights.sbomify.com/CVE-2025-0672/index.md)","id":"CVE-2025-0672","markdown":"https://insights.sbomify.com/CVE-2025-0672/index.md","name":"CVE-2025-0672","record":{"aliases":["GHSA-gf54-37hh-j4g4"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WSO2 Identity Server","requires_auth":"high_privilege","summary":"Attackers can impersonate new users by reusing FIDO credentials from deleted accounts, requiring FIDO authentication to be enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WSO2","cpe":[{"product":"identity_server","vendor":"wso2"},{"product":"identity_server_as_key_manager","vendor":"wso2"},{"product":"open_banking_iam","vendor":"wso2"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An authentication bypass vulnerability exists in multiple WSO2 products when FIDO authentication is enabled. When a user account is deleted, the system does not automatically remove associated FIDO registration data. If a new user account is later created using the same username, the system may associate the new account with the previously registered FIDO device.\n\nThis flaw may allow a previously deleted user to authenticate using their FIDO credentials and impersonate the newly created user, resulting in unauthorized access. The vulnerability applies only to deployments that utilize FIDO-based authentication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Authentication Bypass in Multiple WSO2 Products via Stale FIDO Credential Association","id":"CVE-2025-0672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wso2:identity_server","products":["wso2:identity_server","wso2:identity_server_as_key_manager"],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Loop with Unreachable Exit Condition ('Infinite Loop') in GitLab","id":"CVE-2025-0673"},"packages":[],"prev":{"headline":"Email Subscribers \u003c 5.7.50 - Admin+ Stored XSS in Template","id":"CVE-2025-0671"},"products":["WSO2 Identity Server","WSO2 Identity Server as Key Manager","WSO2 Open Banking IAM"],"published":"2025-09-23","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2016-4311","kev_date_added":null,"published":"2017-02-16"},{"cvss_score":8.6,"headline":"Denial-of-Service via Magic Link Authentication in WSO2 Identity Server Allows Service Unavailability","id":"CVE-2025-10470","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":8.4,"headline":"Server-Side Template Injection via Velocity Template Engine in Multiple WSO2 Products Allows Remote Code Execution","id":"CVE-2025-12107","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":7.5,"headline":"XML external entity in n/a","id":"CVE-2016-4312","kev_date_added":null,"published":"2017-02-16"},{"cvss_score":7.3,"headline":"Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access","id":"CVE-2025-10908","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":6.8,"headline":"Auth bypass in WSO2 Identity Server","id":"CVE-2025-0663","kev_date_added":null,"published":"2025-09-23"},{"cvss_score":6.5,"headline":"Unauthenticated Server-Side Request Forgery (SSRF) in Multiple WSO2 Products via SOAP Admin Services","id":"CVE-2024-7073","kev_date_added":null,"published":"2025-06-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-25","vendors":["WSO2"]},"summary":"Attackers can impersonate new users by reusing FIDO credentials from deleted accounts, requiring FIDO authentication to be enabled.","url":"https://insights.sbomify.com/CVE-2025-0672/"}