VulnerabilityPublished 6 Aug 2026

CVE-2025-15039: WSO2 Identity Server · Protection Mechanism Failure

Affects WSO2 Identity ServerSource CVE Database V5

Compare

Not known to be exploited · CVSS 9.4 Critical · fixed in 7.2.0.7 : patch WSO2 Identity Server as a priority.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score

9.4Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.2.0.7, 7.1.0.49, 7.1.0.45 +49

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-76r4-x438-gm5w

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 Identity Server	Affected >=7.2.0 <7.2.0.7	Fixed in 7.2.0.7
WSO2WSO2 Identity Server	Affected >=7.1.0 <7.1.0.49	Fixed in 7.1.0.49
WSO2WSO2 Identity Server	Affected >=7.1.0 <7.1.0.45	Fixed in 7.1.0.45
WSO2WSO2 Identity Server	Affected >=7.0.0 <7.0.0.138	Fixed in 7.0.0.138
WSO2WSO2 Identity Server	Affected >=6.1.0 <6.1.0.260	Fixed in 6.1.0.260
WSO2WSO2 Identity Server	Affected >=6.0.0 <6.0.0.259	Fixed in 6.0.0.259

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

CVE-2025-15039 is a critical vulnerability in WSO2 Identity Server affecting multiple versions. It involves a protection mechanism failure in the Conditional Authentication (Adaptive Authentication) script, which does not properly enforce completion of all required authentication steps in certain multi-step authentication flows. This flaw allows attackers to bypass intermediate authentication challenges under specific conditions, potentially gaining unauthorized access to user accounts.

Impact

Successful exploitation leads to unauthorized access to user accounts, compromising confidentiality and integrity of user sessions. The vulnerability has a CVSS 3.1 base score of 9.4 (critical), indicating high impact with network attack vector, no privileges required, no user interaction, and high confidentiality and integrity impact with low availability impact.

Summary

The vulnerability arises from improper enforcement in the Conditional Authentication script of WSO2 Identity Server when configured with a specific multi-step authentication pattern involving certain secondary authenticators. The script mishandles callbacks and re-execution of authentication steps, enabling an attacker who completes preceding steps to bypass intermediate challenges. Exploitation requires the presence of a particular secondary authenticator in the login flow, the use of event callbacks in the script, and the targeted user having an impacted authenticator enrolled. This results in unauthorized access to the targeted user account.

CWE-693Protection Mechanism Failure (opens in a new tab)
Pillar weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Site Tracing (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Encryption Brute Forcing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4973/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Aug 2026, 17:33 UTC

WeaknessesCWE-693

Technical details

References

Community reviews

Related threats