PatchTheCVECVE-2025-8591: The software accepts user-supplied input via a URL parameter without adequate output encoding before reflectin
26
Routine
MEDIUM 6.1UPGRADEUPGRADEUPGRADE
CVE-2025-8591 is a medium-severity flaw (CVSS 6.1) 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 software accepts user-supplied input via a URL parameter without adequate output encoding before reflecting it back to the user's browser. This condition allows an attacker to inject malicious script content into pages served by the application. By leveraging this weakness, an attacker can cause the user's browser to redirect to a malicious website, modify the UI of the webpage, or retrieve information from the browser. However, the impact i
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 83%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2026-07-06 |
| Last modified | 2026-10-06 |
Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
wso2 api control plane UPGRADE
Affected: >= 4.5.0 and < 4.5.0.44 · >= 4.6.0 and < 4.6.0.8
Fixed in: 4.5.0.44, 4.6.0.8
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.44 (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.355 · >= 3.2.0 and < 3.2.0.459 · >= 3.2.1 and < 3.2.1.78 · >= 4.0.0 and < 4.0.0.380 · >= 4.1.0 and < 4.1.0.243 · >= 4.2.0 and < 4.2.0.183 · >= 4.3.0 and < 4.3.0.94 · >= 4.4.0 and < 4.4.0.58
Fixed in: 3.1.0.355, 3.2.0.459, 3.2.1.78, 4.0.0.380, 4.1.0.243, 4.2.0.183, 4.3.0.94, 4.4.0.58, 4.5.0.43, 4.6.0.7
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.355 (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.384 · >= 6.0.0 and < 6.0.0.255 · >= 7.0.0 and < 7.0.0.131 · >= 7.1.0 and < 7.1.0.51
Fixed in: 5.10.0.384, 6.0.0.255, 7.0.0.131, 7.1.0.51
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.384 (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.375
Fixed in: 5.10.0.375
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.375 (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.404
Fixed in: 2.0.0.404
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.404 (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.424
Fixed in: 2.0.0.424
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.424 (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.
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-8591?
api control plane: upgrade to 4.5.0.44, 4.6.0.8; api manager: upgrade to 3.1.0.355, 3.2.0.459, 3.2.1.78, 4.0.0.380, 4.1.0.243, 4.2.0.183, 4.3.0.94, 4.4.0.58, 4.5.0.43, 4.6.0.7; identity server: upgrade to 5.10.0.384, 6.0.0.255, 7.0.0.131, 7.1.0.51. Exact commands for each OS are on this page.
Is CVE-2025-8591 being exploited?
CVE-2025-8591 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-8591 affect?
CVE-2025-8591 affects api control plane, api manager, identity server. Severity is medium (CVSS 6.1). The software accepts user-supplied input via a URL parameter without adequate output encoding before reflecting it back to the user's browser. This condition allows an attacker to inject malicious script content into pages served by the app
How urgent is CVE-2025-8591?
Priority 26/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-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