CVE Intelligence
Low Authentication

CVE-2025-0672 — Authentication Bypass in Multiple WSO2 Products via Stale FIDO Credential Association

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. This 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.

Published Sep 23, 2025 · Updated Oct 18, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: WSO2

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.22%
ahead of 11% of scored CVEs · Oct 18, 2026
Affects
WSO2
Identity Server and 2 more
CVSS base
3.8
Low · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (WSO2 Identity Server, WSO2 Identity Server As Key Manager, WSO2 Open Banking Iam).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
WSO2 Identity Server version 5.10.0version 5.11.0 Vulnerable NIST National Vulnerability Database
WSO2 Identity Server ≥ 5.10.0 and < 5.10.0.345≥ 5.11.0 and < 5.11.0.394 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Identity Server As Key Manager version 5.10.0 Vulnerable NIST National Vulnerability Database
WSO2 Identity Server As Key Manager ≥ 5.10.0 and < 5.10.0.338 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Open Banking Iam version 2.0.0 Vulnerable NIST National Vulnerability Database
WSO2 Open Banking Iam ≥ 2.0.0 and < 2.0.0.389 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
3.8 CVSS 3.1 Low 1.2 2.5 nvd@nist.gov via NIST National Vulnerability Database
3.3 CVSS 3.1 Low 0.7 2.5 ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
3.3 CVSS 3.1 Low — — GitHub, Inc. via GitHub Security Advisories
3.3 CVSS 3.1 Low — — WSO2 via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 3.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-287 · Improper Authentication

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · wso2/wso2 identity server as key manager, wso2/wso2 identity server, wso2/wso2 open banking iam
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 18, 2026
  • Affected products added · wso2/identity server, wso2/identity server as key manager, wso2/open banking iam
    Oct 18, 2026 · NIST National Vulnerability Database
  • CVSS changed · 3.8
    Oct 18, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 18, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 18, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Sep 23, 2025 · WSO2

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 18, 2026 – Oct 18, 2026
  • 1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

4 on the record

Elsewhere on this site

WSO2
every CVE for this vendor
Authentication
same class
CWE-287
other pages naming this weakness

Related CVEs (same products)

  • CVE-2025-7203 Sensitive Information Disclosure via Management Console and Product Files in Multiple WSO2 Products Allows Retrieval of Credentials 4h
  • CVE-2025-13591 Username Enumeration via Authentication Endpoint in WSO2 Identity Server Allows User Account Discovery 4h
  • CVE-2025-13173 Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination 4h
  • CVE-2025-10149 Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover 4h
  • CVE-2024-4412 Expression Language Injection via User Input in Multiple WSO2 Products Permits Arbitrary Operations 4h
  • CVE-2024-4457 Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-0672 is "Authentication Bypass in Multiple WSO2 Products via Stale FIDO Credential Association", rated Low. It affects Identity Server (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.8 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.