CVE-2025-13394: The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-

Routine

MEDIUM 5.4UPGRADEUPGRADEUPGRADE

CVE-2025-13394 is a medium-severity flaw (CVSS 5.4) 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.

The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-Site Request Forgery (CSRF) attacks. Specifically, it utilizes the HTTP GET method for these operations, and while the SameSite=Lax cookie attribute is employed for mitigation, this mechanism is bypassed as it permits cookies to be sent with cross-origin top-level navigation requests, including GET requests. This allows an attacker to tri

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-352
Published	2026-08-06
Last modified	2026-09-29

Publisher (CNA): WSO2 LLC · Vendor: wso2

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

Am I affected?

Timeline

2026-08-06 08:16 UTCPublished CVE record published
2026-09-29 14:10 UTCUpdated Record last modified

wso2 api control plane UPGRADE

Affected: >= 4.5.0 and < 4.5.0.39 · >= 4.6.0 and < 4.6.0.3

Fixed in: 4.5.0.39, 4.6.0.3

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. UPGRADE to 4.5.0.39 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade api-control-plane

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade api-control-plane

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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 UPGRADE

Affected: >= 3.1.0 and < 3.1.0.352 · >= 3.2.0 and < 3.2.0.456 · >= 3.2.1 and < 3.2.1.75 · >= 4.0.0 and < 4.0.0.376 · >= 4.1.0 and < 4.1.0.239 · >= 4.2.0 and < 4.2.0.179 · >= 4.3.0 and < 4.3.0.91 · >= 4.4.0 and < 4.4.0.55

Fixed in: 3.1.0.352, 3.2.0.456, 3.2.1.75, 4.0.0.376, 4.1.0.239, 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.38, 4.6.0.3

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. UPGRADE to 3.1.0.352 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade api-manager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade api-manager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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 UPGRADE

Affected: >= 6.6.0 and < 6.6.0.227

Fixed in: 6.6.0.227

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. UPGRADE to 6.6.0.227 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade enterprise-integrator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade enterprise-integrator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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 UPGRADE

Affected: >= 5.10.0 and < 5.10.0.381 · >= 5.11.0 and < 5.11.0.428 · >= 6.0.0 and < 6.0.0.255 · >= 6.1.0 and < 6.1.0.256 · >= 7.0.0 and < 7.0.0.133 · >= 7.1.0 and < 7.1.0.41 · >= 7.2.0 and < 7.2.0.3

Fixed in: 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.256, 7.0.0.133, 7.1.0.41, 7.2.0.3

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. UPGRADE to 5.10.0.381 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade identity-server

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade identity-server

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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 UPGRADE

Affected: >= 5.10.0 and < 5.10.0.372

Fixed in: 5.10.0.372

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. UPGRADE to 5.10.0.372 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade identity-server-as-key-manager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade identity-server-as-key-manager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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 UPGRADE

Affected: >= 2.0.0 and < 2.0.0.401

Fixed in: 2.0.0.401

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. UPGRADE to 2.0.0.401 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade open-banking-am

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade open-banking-am

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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-13394?

api control plane: upgrade to 4.5.0.39, 4.6.0.3; api manager: upgrade to 3.1.0.352, 3.2.0.456, 3.2.1.75, 4.0.0.376, 4.1.0.239, 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.38, 4.6.0.3; enterprise integrator: upgrade to 6.6.0.227. Exact commands for each OS are on this page.

Is CVE-2025-13394 being exploited?

CVE-2025-13394 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-13394 affect?

CVE-2025-13394 affects api control plane, api manager, enterprise integrator. Severity is medium (CVSS 5.4). The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-Site Request Forgery (CSRF) attacks. Specifically, it utilizes the HTTP GET method for these operations, and while the SameSite=La

How urgent is CVE-2025-13394?

Priority 20/100. No elevated risk signals yet.

Related CVEs

CVE-2025-12737 HIGH 8.4 UPGRADE UPGRADE The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu
CVE-2025-15039 CRITICAL 9.4 UPGRADE UPGRADE The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of a
CVE-2026-5430 CRITICAL 10.0 EXPLOITED UPGRADE UPGRADE WSO2 Multiple Products Path Traversal Vulnerability
CVE-2026-3416 MEDIUM 5.9 UPGRADE UPGRADE The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create
CVE-2026-2445 MEDIUM 6.1 UPGRADE UPGRADE The affected product accepts user-supplied input within a URL parameter without enforcing expected sanitizatio

References

← Back to latest CVEs