CVE-2025-14260
Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources
Due to the improper implementation of access control rules, malicious actors could perform a Server Side Request Forgery (SSRF) attack on affected WSO2 Products. Exploiting this vulnerability allows a malicious actor to access both internal and external resources, available through the network or filesystem. This could potentially lead to unauthorized access to sensitive data and systems, regardless of whether these resources are located within a private network, as long as they are reachable by the WSO2 product.
Fixes and workarounds
Fix
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4050/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4050/#solution
Source: CNA: WSO2Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| WSO2 API Manager WSO2 |
≥ 0; < 3.1.0 (unknown, custom) ≥ 3.1.0; < 3.1.0.354 (affected, custom) ≥ 3.2.0; < 3.2.0.458 (affected, custom) ≥ 3.2.1; < 3.2.1.99 (affected, custom) ≥ 4.0.0; < 4.0.0.379 (affected, custom) ≥ 4.1.0; < 4.1.0.265 (affected, custom) ≥ 4.2.0; < 4.2.0.205 (affected, custom) ≥ 4.3.0; < 4.3.0.115 (affected, custom) ≥ 4.4.0; < 4.4.0.79 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Identity Server as Key Manager WSO2 |
≥ 0; < 5.10.0 (unknown, custom) ≥ 5.10.0; < 5.10.0.374 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Open Banking AM WSO2 |
≥ 0; < 2.0.0 (unknown, custom) ≥ 2.0.0; < 2.0.0.403 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Open Banking IAM WSO2 |
≥ 0; < 2.0.0 (unknown, custom) ≥ 2.0.0; < 2.0.0.423 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Identity Server WSO2 |
≥ 0; < 5.10.0 (unknown, custom) ≥ 5.10.0; < 5.10.0.383 (affected, custom) ≥ 5.11.0; < 5.11.0.430 (affected, custom) ≥ 6.0.0; < 6.0.0.256 (affected, custom) ≥ 6.1.0; < 6.1.0.257 (affected, custom) ≥ 7.0.0; < 7.0.0.134 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| SAML2 SSO Authenticator UI Bundle WSO2 org.wso2.carbon.identity:org.wso2.carbon.identity.authenticator.saml2.sso.ui
|
≥ 5.5.0; < 5.5.0.2 (affected, custom) ≥ 5.5.2; < 5.5.2.5 (affected, custom) ≥ 5.5.9; < 5.5.9.4 (affected, custom) ≥ 5.5.10; < 5.5.10.1 (affected, custom) ≥ 5.6.4; < 5.6.4.1 (affected, custom) ≥ 5.7.2; < 5.7.2.1 (affected, custom) ≥ 5.8.3; < 5.8.3.1 (affected, custom) ≥ 5.8.7; < 5.8.7.2 (affected, custom) ≥ 5.9.4; < 5.9.4.2 (affected, custom) ≥ 5.9.9; ≤ * (unaffected, custom) Other versions: unknown |
CNA: WSO2 |
| WSO2 Carbon UI WSO2 org.wso2.carbon:org.wso2.carbon.ui
|
≥ 4.6.0; < 4.6.0.2300 (affected, custom) ≥ 4.6.1; < 4.6.1.165 (affected, custom) ≥ 4.6.3; < 4.6.3.46 (affected, custom) ≥ 4.6.4; < 4.6.4.28 (affected, custom) ≥ 4.7.1; < 4.7.1.79 (affected, custom) ≥ 4.8.1; < 4.8.1.50 (affected, custom) ≥ 4.9.0; < 4.9.0.107 (affected, custom) ≥ 4.9.26; < 4.9.26.37 (affected, custom) ≥ 4.9.27; < 4.9.27.24 (affected, custom) ≥ 4.10.9; < 4.10.9.77 (affected, custom) ≥ 4.10.42; ≤ * (unaffected, custom) Other versions: unknown |
CNA: WSO2 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.3 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L | CNA: WSO2 |
| 3.1 / 8.3 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L | NVD: ed10eef1-636d-4fbe-9993-6890dfa878f8 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4050/CNA: WSO2 · vendor-advisory
- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4050/ed10eef1-636d-4fbe-9993-6890dfa878f8
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.