CVE-2025-15039: Wso2 API Manager vulnerability (CVSS 9.4)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityLow

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

Affected products

Wso2 API Control Plane≥ 4.5.0 < 4.5.0.45 · ≥ 4.6.0 < 4.6.0.9

Wso2 API Manager≥ 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

Wso2 Identity Server≥ 5.10.0 < 5.10.0.385 · ≥ 5.11.0 < 5.11.0.432 · ≥ 5.7.0 < 5.7.0.130 · ≥ 5.8.0 < 5.8.0.133

Wso2 Identity Server As Key Manager≥ 5.10.0 < 5.10.0.376 · ≥ 5.7.0 < 5.7.0.129 · ≥ 5.9.0 < 5.9.0.179

Wso2 Open Banking Am≥ 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.425

Wso2 Open Banking Km≥ 1.4.0 < 1.4.0.137 · ≥ 1.5.0 < 1.5.0.127

Wso2 Traffic Manager≥ 4.5.0 < 4.5.0.43 · ≥ 4.6.0 < 4.6.0.8

Wso2 Universal Gateway≥ 4.5.0 < 4.5.0.44 · ≥ 4.6.0 < 4.6.0.8

Remediation

Fixed in

Wso2 API Control Plane≥ 4.5.0.45

Wso2 API Manager≥ 2.6.0.150

Wso2 Identity Server≥ 5.10.0.385

Wso2 Identity Server As Key Manager≥ 5.10.0.376

Wso2 Open Banking Am≥ 1.4.0.143

Wso2 Open Banking Iam≥ 2.0.0.425

Wso2 Open Banking Km≥ 1.4.0.137

Wso2 Traffic Manager≥ 4.5.0.43

Wso2 Universal Gateway≥ 4.5.0.44

Patch & vendor advisories

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4973/

References

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4973/Vendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-15039 being actively exploited?

CVE-2025-15039 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.67%.

How severe is CVE-2025-15039?

CVE-2025-15039 has a CVSS 3.1 base score of 9.4, rated critical. EPSS estimates a 0.67% probability of exploitation.

Which products are affected by CVE-2025-15039?

Affected products include Wso2 API Control Plane, Wso2 API Manager, Wso2 Identity Server, Wso2 Identity Server As Key Manager, Wso2 Open Banking Am, and 4 more.

How do I fix CVE-2025-15039?

Upgrade affected software to a fixed version, for example Wso2 API Control Plane 4.5.0.45, Wso2 API Manager 2.6.0.150, Wso2 Identity Server 5.10.0.385 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-15039 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo