CVE-2025-12737: The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu

Routine

HIGH 8.4UPGRADEUPGRADEUPGRADE

CVE-2025-12737 is a high-severity flaw (CVSS 8.4) affecting api control plane, api manager, identity server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative operations, leading to a complete compromise of t

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.4 (High)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.4% (top 69%)
CISA exploited list	No
Weakness	CWE-78
Published	2026-09-03
Last modified	2026-10-19

Publisher (CNA): WSO2 LLC · Vendor: wso2

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

Am I affected?

Timeline

2026-09-03 14:17 UTCPublished CVE record published
2026-10-19 22:10 UTCUpdated Record last modified

wso2 api control plane UPGRADE

Affected: >= 4.5.0 and < 4.5.0.36 · 4.6.0

Fixed in: 4.5.0.36

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.36 (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.349 · >= 3.2.0 and < 3.2.0.453 · >= 3.2.1 and < 3.2.1.73 · >= 4.0.0 and < 4.0.0.373 · >= 4.1.0 and < 4.1.0.236 · >= 4.2.0 and < 4.2.0.176 · >= 4.3.0 and < 4.3.0.88 · >= 4.4.0 and < 4.4.0.52

Fixed in: 3.1.0.349, 3.2.0.453, 3.2.1.73, 4.0.0.373, 4.1.0.236, 4.2.0.176, 4.3.0.88, 4.4.0.52, 4.5.0.35

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.349 (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 identity server UPGRADE

Affected: >= 5.10.0 and < 5.10.0.378 · >= 5.11.0 and < 5.11.0.425 · >= 6.0.0 and < 6.0.0.252 · >= 6.1.0 and < 6.1.0.253 · >= 7.0.0 and < 7.0.0.130 · >= 7.1.0 and < 7.1.0.38 · 7.2.0

Fixed in: 5.10.0.378, 5.11.0.425, 6.0.0.252, 6.1.0.253, 7.0.0.130, 7.1.0.38

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.378 (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.369

Fixed in: 5.10.0.369

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.369 (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.398

Fixed in: 2.0.0.398

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.398 (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.

wso2 open banking iam UPGRADE

Affected: >= 2.0.0 and < 2.0.0.418

Fixed in: 2.0.0.418

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy open-banking-iam || rpm -q open-banking-iam || open-banking-iam --version

2. UPGRADE to 2.0.0.418 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade open-banking-iam

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-iam sudo apt install open-banking-iam=<VERSION_BEFORE_2.0.0> sudo apt-mark hold open-banking-iam

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list open-banking-iam sudo dnf downgrade open-banking-iam-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add open-banking-iam

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-12737?

api control plane: upgrade to 4.5.0.36; api manager: upgrade to 3.1.0.349, 3.2.0.453, 3.2.1.73, 4.0.0.373, 4.1.0.236, 4.2.0.176, 4.3.0.88, 4.4.0.52, 4.5.0.35; identity server: upgrade to 5.10.0.378, 5.11.0.425, 6.0.0.252, 6.1.0.253, 7.0.0.130, 7.1.0.38. Exact commands for each OS are on this page.

Is CVE-2025-12737 being exploited?

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

CVE-2025-12737 affects api control plane, api manager, identity server. Severity is high (CVSS 8.4). The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successf

How urgent is CVE-2025-12737?

Priority 37/100. High severity

Related CVEs

CVE-2025-15039 CRITICAL 9.4 UPGRADE UPGRADE The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of a
CVE-2025-13394 MEDIUM 5.4 UPGRADE UPGRADE The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-
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