CyberSecBulletin
CVE-2025-6670NVD status: Analyzed

WSO2 Open Banking AM: Cross-Site Request Forgery

Published Updated By the CyberSecBulletin desk

CVE-2025-6670 is a high-severity cross-site request forgery vulnerability in WSO2 Open Banking AM from WSO2, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. There is no confirmed exploitation so far. EPSS estimates a 0.25% 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 Traffic Manager to 4.5.0.34 or 4.6.0.1, whichever matches your release line, or a later version.
  2. Update WSO2 Universal Gateway to 4.5.0.34 or 4.6.0.1, whichever matches your release line, or a later version.
  3. Update WSO2 API Control Plane to 4.5.0.36 or 4.6.0.1, whichever matches your release line, or a later version.
  4. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  6. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 Open Banking AMNot specified in the recordNot stated
WSO2WSO2 Open Banking IAMNot specified in the recordNot stated
WSO2WSO2 Traffic Manager4.5.0 up to, but not including, 4.5.0.34; 4.6.0 up to, but not including, 4.6.0.14.5.0.34, 4.6.0.1
WSO2WSO2 Universal Gateway4.5.0 up to, but not including, 4.5.0.34; 4.6.0 up to, but not including, 4.6.0.14.5.0.34, 4.6.0.1
WSO2WSO2 API Control Plane4.5.0 up to, but not including, 4.5.0.36; 4.6.0 up to, but not including, 4.6.0.14.5.0.36, 4.6.0.1
WSO2WSO2 API Manager3.1.0 up to, but not including, 3.1.0.349; 3.2.0 up to, but not including, 3.2.0.453; 3.2.1 up to, but not including, 3.2.1.73; 4.0.0 up to, but not including, 4.0.0.373; 4.1.0 up to, but not including, 4.1.0.236; 4.2.0 up to, but not including, 4.2.0.176; 4.3.0 up to, but not including, 4.3.0.88; 4.4.0 up to, but not including, 4.4.0.52; and 2 more ranges3.1.0.349, 3.2.0.453, 3.2.1.73, 4.0.0.373, 4.1.0.236, 4.2.0.176
WSO2WSO2 Identity Server5.10.0 up to, but not including, 5.10.0.378; 5.11.0 up to, but not including, 5.11.0.425; 6.0.0 up to, but not including, 6.0.0.252; 6.1.0 up to, but not including, 6.1.0.253; 7.0.0 up to, but not including, 7.0.0.130; 7.1.0 up to, but not including, 7.1.0.38; 7.2.0 up to, but not including, 7.2.0.15.10.0.378, 5.11.0.425, 6.0.0.252, 6.1.0.253, 7.0.0.130, 7.1.0.38
WSO2WSO2 Identity Server as Key Manager5.10.0 up to, but not including, 5.10.0.3695.10.0.369
WSO2WSO2 Enterprise Integrator6.6.0 up to, but not including, 6.6.0.2266.6.0.226
WSO2org.wso2.carbon:org.wso2.carbon.ui4.5.3 up to, but not including, 4.5.3.50; 4.6.0 up to, but not including, 4.6.0.2253; 4.6.1 up to, but not including, 4.6.1.157; 4.6.2 up to, but not including, 4.6.2.673; 4.6.3 up to, but not including, 4.6.3.41; 4.6.4 up to, but not including, 4.6.4.22; 4.7.1 up to, but not including, 4.7.1.73; 4.8.1 up to, but not including, 4.8.1.43; and 8 more ranges4.5.3.50, 4.6.0.2253, 4.6.1.157, 4.6.2.673, 4.6.3.41, 4.6.4.22
WSO2API Control Plane4.5.0; 4.6.0Not stated
WSO2API Manager3.1.0; 3.2.0; 3.2.1; 4.0.0; 4.1.0; 4.2.0; 4.3.0; 4.4.0; and 2 more rangesNot stated
WSO2Enterprise Integrator6.6.0Not stated
WSO2Identity Server5.10.0; 5.11.0; 6.0.0; 6.1.0; 7.0.0; 7.1.0; 7.2.0Not stated
WSO2Identity Server As Key Manager5.10.0Not stated
WSO2Open Banking Am2.0.0Not stated
WSO2Open Banking Iam2.0.0Not stated
WSO2Traffic Manager4.5.0; 4.6.0Not stated
WSO2Universal Gateway4.5.0; 4.6.0Not stated

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
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
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
HighThe component can be taken down completely.

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

Official description

A Cross-Site Request Forgery (CSRF) vulnerability exists in multiple WSO2 products due to the use of the HTTP GET method for state-changing operations within admin services, specifically in the event processor of the Carbon console. Although the SameSite=Lax cookie attribute is used as a mitigation, it is ineffective in this context because it allows cookies to be sent with cross-origin top-level navigations using GET requests. A malicious actor can exploit this vulnerability by tricking an authenticated user into visiting a crafted link, leading the browser to issue unintended state-changing requests. Successful exploitation could result in unauthorized operations such as data modification, account changes, or other administrative actions. According to WSO2 Secure Production Guidelines, exposure of Carbon console services to untrusted networks is discouraged, which may reduce the impact in properly secured deployments.

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

The underlying weakness: Cross-Site Request Forgery

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

How developers prevent this class of flaw

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, use anti-CSRF packages such as the OWASP CSRFGuard. Another example is the ESAPI Session Management control, which includes a component for CSRF.
  • Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
  • Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).

More Cross-Site Request Forgery vulnerabilities (CWE-352)

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

Other vulnerabilities in WSO2 Open Banking AM

All WSO2 Open Banking AM vulnerabilities

Recent Cross-Site Request Forgery vulnerabilities

Spotted an error? Tell us.