CVE-2025-6670Cross-Site Request Forgery (CSRF) in Multiple WSO2 Products via HTTP GET in Admin Services

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.25% · top 84% of all CVEs (13 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: total

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

• WSO2 · WSO2 Open Banking AM

  • unknown < 2.0.0
  • unaffected 2.0.0 – < 2.0.0.398

• WSO2 · WSO2 Open Banking IAM

  • unknown < 2.0.0
  • unaffected 2.0.0 – < 2.0.0.418

• WSO2 · WSO2 Traffic Manager

  • affected 4.5.0 – < 4.5.0.34
  • affected 4.6.0 – < 4.6.0.1

• WSO2 · WSO2 Universal Gateway

  • affected 4.5.0 – < 4.5.0.34
  • affected 4.6.0 – < 4.6.0.1

• WSO2 · WSO2 API Control Plane

  • affected 4.5.0 – < 4.5.0.36
  • affected 4.6.0 – < 4.6.0.1

• WSO2 · WSO2 API Manager

  • unknown < 3.1.0
  • affected 3.1.0 – < 3.1.0.349
  • affected 3.2.0 – < 3.2.0.453
  • affected 3.2.1 – < 3.2.1.73
  • affected 4.0.0 – < 4.0.0.373
  • affected 4.1.0 – < 4.1.0.236
  • affected 4.2.0 – < 4.2.0.176
  • affected 4.3.0 – < 4.3.0.88
  • affected 4.4.0 – < 4.4.0.52
  • affected 4.5.0 – < 4.5.0.35
  • affected 4.6.0 – < 4.6.0.1

• WSO2 · WSO2 Identity Server

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.378
  • affected 5.11.0 – < 5.11.0.425
  • affected 6.0.0 – < 6.0.0.252
  • affected 6.1.0 – < 6.1.0.253
  • affected 7.0.0 – < 7.0.0.130
  • affected 7.1.0 – < 7.1.0.38
  • affected 7.2.0 – < 7.2.0.1

• WSO2 · WSO2 Identity Server as Key Manager

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.369

• WSO2 · WSO2 Enterprise Integrator

  • unknown < 6.6.0
  • affected 6.6.0 – < 6.6.0.226

• WSO2 · org.wso2.carbon:org.wso2.carbon.ui

  • affected 4.5.3 – < 4.5.3.50
  • affected 4.6.0 – < 4.6.0.2253
  • affected 4.6.1 – < 4.6.1.157
  • affected 4.6.2 – < 4.6.2.673
  • affected 4.6.3 – < 4.6.3.41
  • affected 4.6.4 – < 4.6.4.22
  • affected 4.7.1 – < 4.7.1.73
  • affected 4.8.1 – < 4.8.1.43
  • affected 4.9.0 – < 4.9.0.106
  • affected 4.9.26 – < 4.9.26.31
  • affected 4.9.27 – < 4.9.27.16
  • affected 4.9.28 – < 4.9.28.18
  • affected 4.9.33 – < 4.9.33.2
  • affected 4.10.9 – < 4.10.9.75
  • affected 4.10.42 – < 4.10.42.18
  • affected 4.10.101 – < 4.10.101.3
  • unaffected 4.9.29 – ≤ 4.9.29.*
  • unaffected 4.10.65 – ≤ 4.10.*

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4117/#solution

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2025-197976 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2025-6670](https://cveledger.app/badge/CVE-2025-6670.svg)](https://cveledger.app/cve/CVE-2025-6670)

Record last updated 18 Nov 2025, 19:12 UTC.