Skip to main content
CVE-2025-6670VulnerabilityPublished

CVE-2025-6670: WSO2 Open Banking AM · Cross-Site Request Forgery (CSRF)

Affects WSO2 Open Banking AMSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

European organizations should immediately review their deployment of WSO2 products, particularly Open Banking AM, to ensure that Carbon console administrative services are not exposed to untrusted networks or the public internet. Network segmentation and strict firewall rules should be enforced to restrict access to these services only to trusted internal IPs. Administrators should be trained to recognize phishing attempts and avoid clicking on suspicious links. WSO2 should be contacted for patches or updates addressing this vulnerability; if none are available, consider implementing additional CSRF protections such as requiring POST methods with anti-CSRF tokens for state-changing operations. Web Application Firewalls (WAFs) can be configured to detect and block suspicious GET requests to admin endpoints. Monitoring and logging of administrative actions should be enhanced to detect anomalous activities promptly. Finally, organizations should review cookie settings and consider additional security headers or mechanisms to mitigate CSRF risks beyond SameSite=Lax.

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.

References

Community reviews

Loading reviews…