cve.bz

CVE-2025-6670 wso2: Cross Site Reference Forgery

8.8 highEPSS 0.2%Fix available

High (8.8) in wso2. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-6670 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-6670?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-6670?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-6670 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
WSO2 Traffic Managerfrom 4.5.0 before 4.5.0.34
WSO2 Traffic Managerfrom 4.6.0 before 4.6.0.1
WSO2 Universal Gatewayfrom 4.5.0 before 4.5.0.34
WSO2 Universal Gatewayfrom 4.6.0 before 4.6.0.1
WSO2 API Control Planefrom 4.5.0 before 4.5.0.36
WSO2 API Control Planefrom 4.6.0 before 4.6.0.1
WSO2 API Managerfrom 3.1.0 before 3.1.0.349
WSO2 API Managerfrom 3.2.0 before 3.2.0.453
WSO2 API Managerfrom 3.2.1 before 3.2.1.73
WSO2 API Managerfrom 4.0.0 before 4.0.0.373
WSO2 API Managerfrom 4.1.0 before 4.1.0.236
WSO2 API Managerfrom 4.2.0 before 4.2.0.176
WSO2 API Managerfrom 4.3.0 before 4.3.0.88
WSO2 API Managerfrom 4.4.0 before 4.4.0.52
WSO2 API Managerfrom 4.5.0 before 4.5.0.35
WSO2 API Managerfrom 4.6.0 before 4.6.0.1
WSO2 Identity Serverfrom 5.10.0 before 5.10.0.378
WSO2 Identity Serverfrom 5.11.0 before 5.11.0.425
WSO2 Identity Serverfrom 6.0.0 before 6.0.0.252
WSO2 Identity Serverfrom 6.1.0 before 6.1.0.253
WSO2 Identity Serverfrom 7.0.0 before 7.0.0.130
WSO2 Identity Serverfrom 7.1.0 before 7.1.0.38
WSO2 Identity Serverfrom 7.2.0 before 7.2.0.1
WSO2 Identity Server as Key Managerfrom 5.10.0 before 5.10.0.369
WSO2 Enterprise Integratorfrom 6.6.0 before 6.6.0.226
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.5.3 before 4.5.3.50
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.6.0 before 4.6.0.2253
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.6.1 before 4.6.1.157
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.6.2 before 4.6.2.673
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.6.3 before 4.6.3.41
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.6.4 before 4.6.4.22
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.7.1 before 4.7.1.73
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.8.1 before 4.8.1.43
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.9.0 before 4.9.0.106
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.9.26 before 4.9.26.31
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.9.27 before 4.9.27.16
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.9.28 before 4.9.28.18
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.9.33 before 4.9.33.2
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.10.9 before 4.10.9.75
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.10.42 before 4.10.42.18
WSO2 org.wso2.carbon:org.wso2.carbon.uifrom 4.10.101 before 4.10.101.3

Fixed in

ProductRelease lineFixed in
WSO2 Open Banking AMlater releases2.0.0
WSO2 Open Banking IAMlater releases2.0.0
WSO2 org.wso2.carbon:org.wso2.carbon.ui4.9.294.9.29
WSO2 org.wso2.carbon:org.wso2.carbon.ui4.104.10.65

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON