BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-15039High confidence

Account Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products

WSO2 · WSO2 Identity Server

9.4CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.67% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs WSO2 WSO2 Identity Server and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-210632

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unauthorized access to a targeted user account. This vulnerability can only be exploited when all of the following conditions are met: the application login flow contains a specific secondary authenticator, the Conditional Authentication script is configured with particular event callbacks and re-executes an authentication step, the targeted user has one of the impacted authenticators enrolled, and the attacker successfully completes any preceding authentication steps.

What

The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unauthorized access to a targeted user account. This vulnerability can only be exploited when all of the following conditions are met: the application login flow contains a specific secondary authenticator, the Conditional Authentication script is configured with particular event callbacks and re-executes an authentication step, the targeted user has one of the impacted authenticators enrolled, and the attacker successfully completes any preceding authentication steps.

Why

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unauthorized access to a targeted user account. This vulnerability can only be exploited when all of the following conditions are met: the application login flow contains a specific secondary authenticator, the Conditional Authentication script is configured with particular event callbacks and re-executes an authentication step, the targeted user has one of the impacted authenticators enrolled, and the attacker successfully completes any preceding authentication steps.

Why

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Protection Mechanism Failure → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-693 ↗

CWE-693: Protection Mechanism Failure. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-693
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Aug 2026, published on 12 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028143WSO2のWSO2 API Control Plane等の複数製品における保護メカニズムの不具合に関する脆弱性

条件付き認証(アダプティブ認証)スクリプトは、特定の認証器を含む複数段階のパターンが設定されている場合に、すべての必要な認証ステップの完了を正しく強制しません。これにより、攻撃者はスクリプトのコールバック処理および認証ステップの再実行の仕組みを悪用して、中間の認証チャレンジを回避できます。この脆弱性を悪用されると、悪意のある攻撃者が対象ユーザーアカウントに不正アクセスを獲得する可能性があります。この脆弱性は、以下のすべての条件が満たされた場合にのみ悪用可能です。すなわち、アプリケーションのログインフローに特定の二次認証器が含まれていること、条件付き認証スクリプトが特定のイベントコールバックで設定されており認証ステップを再実行していること、対象ユーザーが影響を受ける認証器のいずれかを登録していること、そして攻撃者が事前の認証ステップをすべて正常に完了させていることが条件です。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
WSO2 Carbon Identity Application Authentication Framework: 5.25.738 ≤ 5.25.*, 7.8.646 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 6 Aug 2026 · Last source change 6 Aug 2026, 12:31 UTC · CWE-693 · Protection Mechanism Failure

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-210632
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: security.docs.wso2.com/WSO2-2025-4973.
    Before
    vendor advisory: security.docs.wso2.com/WSO2-2025-4973
    After
    remediation: security.docs.wso2.com/WSO2-2025-4973 · vendor advisory: security.docs.wso2.com/WSO2-2025-4973
    security.docs.wso2.com ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 5.7.0; 5.7.0 < 5.7.0.130; 5.8.0 < 5.8.0.113; 5.9.0 < 5.9.0.173; 5.10.0 < 5.10.0.385; 5.11.0 < 5.11.0.432; 6.0.0 < 6.0.0.259; 6.1.0 < 6.1.0.260 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    WSO2 Identity Server: < 5.7.0, 5.7.0 < 5.7.0.130, 5.8.0 < 5.8.0.113, 5.9.0 < 5.9.0.173, 5.10.0 < 5.10.0.385, 5.11.0 < 5.11.0.432, 6.0.0 < 6.0.0.259, 6.1.0 < 6.1.0.260, 7.0.0 < 7.0.0.138, 7.1.0 < 7.1.0.45, 7.1.0 < 7.1.0.49, 7.2.0 < 7.2.0.7; WSO2 API Manager: < 2.6.0, 2.6.0 < 2.6.0.150, 3.0.0 < 3.0.0.180, 3.1.0 < 3.1.0.356, 3.2.0 < 3.2.0.460, 3.2.1 < 3.2.1.79, 4.0.0 < 4.0.0.381, 4.1.0 < 4.1.0.244, 4.2.0 < 4.2.0.184, 4.3.0 < 4.3.0.95, 4.4.0 < 4.4.0.59, 4.5.0 < 4.5.0.44, 4.6.0 < 4.6.0.8; WSO2 Open Banking AM: < 1.4.0, 1.4.0 < 1.4.0.143, 1.5.0 < 1.5.0.144, 2.0.0 < 2.0.0.405; WSO2 Open Banking IAM: < 2.0.0, 2.0.0 < 2.0.0.425; WSO2 Traffic Manager: < 4.5.0, 4.5.0 < 4.5.0.43, 4.6.0 < 4.6.0.8; WSO2 Universal Gateway: 4.5.0 < 4.5.0.43, 4.5.0 < 4.5.0.44, 4.6.0 < 4.6.0.8; WSO2 API Control Plane: 4.5.0 < 4.5.0.45, 4.6.0 < 4.6.0.9; WSO2 Identity Server as Key Manager: < 5.7.0, 5.7.0 < 5.7.0.129, 5.9.0 < 5.9.0.179, 5.10.0 < 5.10.0.376; WSO2 Open Banking KM: < 1.4.0, 1.4.0 < 1.4.0.137, 1.5.0 < 1.5.0.127; WSO2 Carbon Identity Application Authentication Framework: 5.12.153 < 5.12.153.66, 5.12.387 < 5.12.387.48, 5.14.97 < 5.14.97.94, 5.17.5 < 5.17.5.337, 5.17.118 < 5.17.118.24, 5.18.187 < 5.18.187.334, 5.18.248 < 5.18.248.34, 5.23.8 < 5.23.8.221, 5.24.8 < 5.24.8.29, 5.25.92 < 5.25.92.177, 5.25.705 < 5.25.705.23, 5.25.713 < 5.25.713.12, 5.25.724 < 5.25.724.8, 5.25.736 < 5.25.736.3, 7.0.78 < 7.0.78.171, 7.8.23 < 7.8.23.95, 7.8.586 < 7.8.586.21 · Fixed: WSO2 Carbon Identity Application Authentication Framework: 5.25.738 ≤ 5.25.*, 7.8.646 ≤ *
    CNA ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    security.docs.wso2.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-15039 · cve.blacktree.nl