CVE-2025-14260

Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources

Published Oct 28, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

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, potentially leading 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.

Affected Systems

WSO2 SAML2 SSO Authenticator UI Bundle, WSO2 API Manager, WSO2 Carbon UI, WSO2 Identity Server, WSO2 Identity Server as Key Manager, WSO2 Open Banking AM, and WSO2 Open Banking IAM. No specific version numbers were disclosed in the advisory, so all existing releases of these components could potentially be affected until the patch is applied.

Risk and Exploitability

The vulnerability scores a CVSS of 8.3, indicating a high‑severity risk with high confidentiality impact and no authentication required. The EPSS score, less than 1%, indicates a low probability of exploitation, yet the high severity score and lack of authentication suggest a potentially serious threat if discovered. Because the vulnerability is not listed in CISA’s KEV catalog, no public exploitation reports are yet recorded, yet the attack surface and the possibility of internal reconnaissance make it a significant concern. An attacker can craft a payload that causes the server to load data from arbitrary URLs or internal network addresses, effectively turning the application into a proxy for illicit data retrieval. No additional prerequisites are listed, implying that the exploit can be performed from any network location that can reach the vulnerable service.

Remediation

Vendor Solution

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


OpenCVE Recommended Actions

  • Update all affected WSO2 components to the patched versions issued in advisory WSO2-2025‑4050 by following the instructions on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4050/#solution.
  • If an immediate upgrade is not feasible, restrict outbound network traffic from the vulnerable services by implementing firewall rules that block requests to internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and external hosts that are not part of the trusted namespace.
  • After applying the fix or implementing network restrictions, perform a penetration test or controlled SSRF attempt to confirm that the vulnerability is no longer exploitable.

Generated by OpenCVE AI on November 3, 2026 at 13:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Due to the improper implementation of access control rules, the WSO2 product accepts user-supplied input related to resource location without enforcing expected validation constraints. This can be exploited by an unauthenticated actor to direct the server to make requests to arbitrary network locations. Exploiting this vulnerability allows a malicious actor to access both internal and external resources, available through the network or filesystem, that are reachable by the WSO2 product. This could potentially lead to unauthorized access to sensitive data and systems. 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.
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wso2 api Manager
Wso2 identity Server
Wso2 wso2 Carbon Task Ui
Vendors & Products Wso2 api Manager
Wso2 identity Server
Wso2 wso2 Carbon Task Ui
Type Values Removed Values Added
Description Due to the improper implementation of access control rules, the WSO2 product accepts user-supplied input related to resource location without enforcing expected validation constraints. This can be exploited by an unauthenticated actor to direct the server to make requests to arbitrary network locations. Exploiting this vulnerability allows a malicious actor to access both internal and external resources, available through the network or filesystem, that are reachable by the WSO2 product. This could potentially lead to unauthorized access to sensitive data and systems.
Title Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources
First Time appeared Wso2
Wso2 saml2 Sso Authenticator Ui Bundle
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Ui
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Weaknesses CWE-918
CPEs cpe:2.3:a:wso2:saml2_sso_authenticator_ui_bundle:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_api_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_carbon_ui:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server_as_key_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_open_banking_am:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_open_banking_iam:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 saml2 Sso Authenticator Ui Bundle
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Ui
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
References
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L'}