CyberSecBulletin
CVE-2025-14260NVD status: Awaiting Analysis

WSO2 API Manager: Server-Side Request Forgery

Published Updated By the CyberSecBulletin desk

CVE-2025-14260 is a high-severity server-side request forgery vulnerability in WSO2 API Manager from WSO2, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 3.1.0.354, 3.2.0.458, 3.2.1.99 as the first without the flaw, so updating WSO2 API Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.28% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update WSO2 API Manager to 3.1.0.354 or 3.2.0.458 or 3.2.1.99 or 4.0.0.379, whichever matches your release line, or a later version.
  2. Update WSO2 Identity Server as Key Manager to 5.10.0.374 or a later version.
  3. Update WSO2 Open Banking AM to 2.0.0.403 or a later version.
  4. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 API Manager3.1.0 up to, but not including, 3.1.0.354; 3.2.0 up to, but not including, 3.2.0.458; 3.2.1 up to, but not including, 3.2.1.99; 4.0.0 up to, but not including, 4.0.0.379; 4.1.0 up to, but not including, 4.1.0.265; 4.2.0 up to, but not including, 4.2.0.205; 4.3.0 up to, but not including, 4.3.0.115; 4.4.0 up to, but not including, 4.4.0.793.1.0.354, 3.2.0.458, 3.2.1.99, 4.0.0.379, 4.1.0.265, 4.2.0.205
WSO2WSO2 Identity Server as Key Manager5.10.0 up to, but not including, 5.10.0.3745.10.0.374
WSO2WSO2 Open Banking AM2.0.0 up to, but not including, 2.0.0.4032.0.0.403
WSO2WSO2 Open Banking IAM2.0.0 up to, but not including, 2.0.0.4232.0.0.423
WSO2WSO2 Identity Server5.10.0 up to, but not including, 5.10.0.383; 5.11.0 up to, but not including, 5.11.0.430; 6.0.0 up to, but not including, 6.0.0.256; 6.1.0 up to, but not including, 6.1.0.257; 7.0.0 up to, but not including, 7.0.0.1345.10.0.383, 5.11.0.430, 6.0.0.256, 6.1.0.257, 7.0.0.134
WSO2SAML2 SSO Authenticator UI Bundle5.5.0 up to, but not including, 5.5.0.2; 5.5.2 up to, but not including, 5.5.2.5; 5.5.9 up to, but not including, 5.5.9.4; 5.5.10 up to, but not including, 5.5.10.1; 5.6.4 up to, but not including, 5.6.4.1; 5.7.2 up to, but not including, 5.7.2.1; 5.8.3 up to, but not including, 5.8.3.1; 5.8.7 up to, but not including, 5.8.7.2; and 1 more ranges5.5.0.2, 5.5.2.5, 5.5.9.4, 5.5.10.1, 5.6.4.1, 5.7.2.1
WSO2WSO2 Carbon UI4.6.0 up to, but not including, 4.6.0.2300; 4.6.1 up to, but not including, 4.6.1.165; 4.6.3 up to, but not including, 4.6.3.46; 4.6.4 up to, but not including, 4.6.4.28; 4.7.1 up to, but not including, 4.7.1.79; 4.8.1 up to, but not including, 4.8.1.50; 4.9.0 up to, but not including, 4.9.0.107; 4.9.26 up to, but not including, 4.9.26.37; and 2 more ranges4.6.0.2300, 4.6.1.165, 4.6.3.46, 4.6.4.28, 4.7.1.79, 4.8.1.50

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA.

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Server-Side Request Forgery

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

How developers prevent this class of flaw

  • If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
  • If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.

More Server-Side Request Forgery vulnerabilities (CWE-918)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Our coverage

Other vulnerabilities in WSO2 API Manager

All WSO2 API Manager vulnerabilities

Recent Server-Side Request Forgery vulnerabilities

Spotted an error? Tell us.