PatchTheCVECVE-2024-7096: A privilege escalation vulnerability exists in multiple WSO2 products due to a business logic flaw in SOAP adm
28
Routine
MEDIUM 4.2DOWNGRADEDOWNGRADEDOWNGRADE
CVE-2024-7096 is a medium-severity flaw (CVSS 4.2) affecting api manager, identity server, identity server as key manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A privilege escalation vulnerability exists in multiple WSO2 products due to a business logic flaw in SOAP admin services. A malicious actor can create a new user with elevated permissions only when all of the following conditions are met: * SOAP admin services are accessible to the attacker. * The deployment includes an internally used attribute that is not part of the default WSO2 product configuration. * At least one custom role exist
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 4.2 (Medium) |
| Attack vector | Adjacent network |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.7% (top 45%) |
| CISA exploited list | No |
| Weakness | CWE-863 |
| Published | 2025-05-30 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · 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 manager DOWNGRADE
Affected: 2.0.0 · 2.1.0 · 2.2.0 · 2.5.0 · 2.6.0 · 3.0.0 · 3.1.0 · 3.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.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 2.0.0 (Debian / Ubuntu)
apt-cache madison api-manager
sudo apt install api-manager=<VERSION_BEFORE_2.0.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_2.0.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 DOWNGRADE
Affected: 5.2.0 · 5.3.0 · 5.4.0 · 5.4.1 · 5.5.0 · 5.6.0 · 5.7.0 · 5.8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.2.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.2.0 (Debian / Ubuntu)
apt-cache madison identity-server
sudo apt install identity-server=<VERSION_BEFORE_5.2.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.2.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.3.0 · 5.5.0 · 5.6.0 · 5.7.0 · 5.9.0 · 5.10.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.3.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.3.0 (Debian / Ubuntu)
apt-cache madison identity-server-as-key-manager
sudo apt install identity-server-as-key-manager=<VERSION_BEFORE_5.3.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.3.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: 1.3.0 · 1.4.0 · 1.5.0 · 2.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.3.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 1.3.0 (Debian / Ubuntu)
apt-cache madison open-banking-am
sudo apt install open-banking-am=<VERSION_BEFORE_1.3.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_1.3.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 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-iam || rpm -q open-banking-iam || open-banking-iam --version
2. No fixed release: 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
2. No fixed release: 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.
wso2 open banking km DOWNGRADE
Affected: 1.3.0 · 1.4.0 · 1.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.3.0
1. Check installed version
apt-cache policy open-banking-km || rpm -q open-banking-km || open-banking-km --version
2. No fixed release: DOWNGRADE to a release before 1.3.0 (Debian / Ubuntu)
apt-cache madison open-banking-km
sudo apt install open-banking-km=<VERSION_BEFORE_1.3.0>
sudo apt-mark hold open-banking-km
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list open-banking-km
sudo dnf downgrade open-banking-km-<VERSION_BEFORE_1.3.0>
sudo dnf versionlock add open-banking-km
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-2024-7096?
api manager: downgrade or apply the listed mitigation; identity server: downgrade or apply the listed mitigation; identity server as key manager: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2024-7096 being exploited?
CVE-2024-7096 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-2024-7096 affect?
CVE-2024-7096 affects api manager, identity server, identity server as key manager. Severity is medium (CVSS 4.2). A privilege escalation vulnerability exists in multiple WSO2 products due to a business logic flaw in SOAP admin services. A malicious actor can create a new user with elevated permissions only when all of the following conditions are met:
How urgent is CVE-2024-7096?
Priority 28/100. No elevated risk signals yet.
Related CVEs
- CVE-2024-6832 MEDIUM 5.9 DOWNGRADE DOWNGRADE The account locking mechanism fails to trigger when secondary user stores are inaccessible
- CVE-2024-10302 MEDIUM 4.0 DOWNGRADE DOWNGRADE The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input
- CVE-2024-8995 MEDIUM 4.9 UPGRADE UPGRADE Unused authorization codes issued to deleted users are not being properly invalidated or removed from the syst
- CVE-2026-2053 HIGH 8.3 UPGRADE The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently va
- CVE-2025-12737 HIGH 8.4 UPGRADE UPGRADE The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu