Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.2% (top 84%)
CISA exploited listNo
WeaknessCWE-352
Published2025-11-18
Last modified2026-06-17
Publisher (CNA): WSO2 LLC · Vendor: wso2

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

wso2 api control plane DOWNGRADE
Affected: 4.5.0 · 4.6.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy api-control-plane || rpm -q api-control-plane || api-control-plane --version
2. No fixed release: DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison api-control-plane sudo apt install api-control-plane=<VERSION_BEFORE_4.5.0> sudo apt-mark hold api-control-plane
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-control-plane sudo dnf downgrade api-control-plane-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add api-control-plane
Downgrade risk
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.
wso2 api manager DOWNGRADE
Affected: 3.1.0 · 3.2.0 · 3.2.1 · 4.0.0 · 4.1.0 · 4.2.0 · 4.3.0 · 4.4.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.1.0
1. Check installed version
apt-cache policy api-manager || rpm -q api-manager || api-manager --version
2. No fixed release: DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)
apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_3.1.0> sudo apt-mark hold api-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-manager sudo dnf downgrade api-manager-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add api-manager
Downgrade risk
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.
wso2 enterprise integrator DOWNGRADE
Affected: 6.6.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.6.0
1. Check installed version
apt-cache policy enterprise-integrator || rpm -q enterprise-integrator || enterprise-integrator --version
2. No fixed release: DOWNGRADE to a release before 6.6.0 (Debian / Ubuntu)
apt-cache madison enterprise-integrator sudo apt install enterprise-integrator=<VERSION_BEFORE_6.6.0> sudo apt-mark hold enterprise-integrator
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list enterprise-integrator sudo dnf downgrade enterprise-integrator-<VERSION_BEFORE_6.6.0> sudo dnf versionlock add enterprise-integrator
Downgrade risk
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.
wso2 identity server DOWNGRADE
Affected: 5.10.0 · 5.11.0 · 6.0.0 · 6.1.0 · 7.0.0 · 7.1.0 · 7.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.10.0
1. Check installed version
apt-cache policy identity-server || rpm -q identity-server || identity-server --version
2. No fixed release: DOWNGRADE to a release before 5.10.0 (Debian / Ubuntu)
apt-cache madison identity-server sudo apt install identity-server=<VERSION_BEFORE_5.10.0> sudo apt-mark hold identity-server
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list identity-server sudo dnf downgrade identity-server-<VERSION_BEFORE_5.10.0> sudo dnf versionlock add identity-server
Downgrade risk
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.
wso2 identity server as key manager DOWNGRADE
Affected: 5.10.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.10.0
1. Check installed version
apt-cache policy identity-server-as-key-manager || rpm -q identity-server-as-key-manager || identity-server-as-key-manager --version
2. No fixed release: DOWNGRADE to a release before 5.10.0 (Debian / Ubuntu)
apt-cache madison identity-server-as-key-manager sudo apt install identity-server-as-key-manager=<VERSION_BEFORE_5.10.0> sudo apt-mark hold identity-server-as-key-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list identity-server-as-key-manager sudo dnf downgrade identity-server-as-key-manager-<VERSION_BEFORE_5.10.0> sudo dnf versionlock add identity-server-as-key-manager
Downgrade risk
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.
wso2 open banking am DOWNGRADE
Affected: 2.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy open-banking-am || rpm -q open-banking-am || open-banking-am --version
2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison open-banking-am sudo apt install open-banking-am=<VERSION_BEFORE_2.0.0> sudo apt-mark hold open-banking-am
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list open-banking-am sudo dnf downgrade open-banking-am-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add open-banking-am
Downgrade risk
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 source NVD · 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

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.