CVE-2025-6670: Cross-Site Request Forgery (CSRF) in Multiple WSO2 Products via HTTP GET in Admin Services
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.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-6670?
CVE-2025-6670 is classified as a moderate severity vulnerability due to its potential for Cross-Site Request Forgery attacks.
How do I fix CVE-2025-6670?
To fix CVE-2025-6670, it is recommended to update to the latest version of WSO2 products that address this vulnerability.
What is the impact of CVE-2025-6670 on WSO2 Carbon Console?
CVE-2025-6670 can allow attackers to perform unauthorized actions if exploited, potentially compromising the security of admin services.
Which WSO2 products are affected by CVE-2025-6670?
CVE-2025-6670 affects multiple WSO2 products, specifically those utilizing the Carbon Console for administrative tasks.
How can I detect if my system is vulnerable to CVE-2025-6670?
You can detect vulnerability to CVE-2025-6670 by reviewing your WSO2 deployment for the use of HTTP GET requests for state-changing operations.