CVE-2025-6670: A Cross-Site Request Forgery (CSRF) vulnerability exists in multiple WSO2 products due to the use of the HTTP
35
Routine
HIGH 8.8DOWNGRADEDOWNGRADEDOWNGRADE
CVE-2025-6670 is a high-severity flaw (CVSS 8.8) affecting api control plane, api manager, enterprise integrator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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
Why this priority
High severity
No fix is published yet: follow the downgrade or mitigation steps.
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official sourceNVD · CVE Program · Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-6670?
api control plane: downgrade or apply the listed mitigation; api manager: downgrade or apply the listed mitigation; enterprise integrator: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-6670 being exploited?
CVE-2025-6670 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-6670 affect?
CVE-2025-6670 affects api control plane, api manager, enterprise integrator. Severity is high (CVSS 8.8). 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. Althoug
How urgent is CVE-2025-6670?
Priority 35/100. High severity
Related CVEs
CVE-2024-6832MEDIUM 5.9DOWNGRADEDOWNGRADE The account locking mechanism fails to trigger when secondary user stores are inaccessible
CVE-2024-10302MEDIUM 4.0DOWNGRADEDOWNGRADE The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input
CVE-2024-8995MEDIUM 4.9UPGRADEUPGRADE Unused authorization codes issued to deleted users are not being properly invalidated or removed from the syst
CVE-2025-12737HIGH 8.4UPGRADEUPGRADE The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu
CVE-2025-9152CRITICAL 9.8DOWNGRADEDOWNGRADE An improper privilege management vulnerability exists in WSO2 API Manager due to missing authentication and au