CVE-2024-2374: The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to pr

Routine

HIGH 7.5REMOTEUPGRADEUPGRADEUPGRADE

CVE-2024-2374 is a high-severity flaw (CVSS 7.5) 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.

The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the resolution of external entities. This omission allows malicious actors to craft XML payloads that exploit the parser's behavior, leading to the inclusion of external resources. By leveraging this vulnerability, an attacker can read confidential files from the file system and access limited HTTP resources reachable by the produc

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 68%)
CISA exploited list	No
Weakness	CWE-611
Published	2026-04-16
Last modified	2026-06-17

Publisher (CNA): WSO2 LLC · Vendor: wso2

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

Am I affected?

Timeline

2026-04-16 09:16 UTCPublished CVE record published
2026-06-17 07:24 UTCUpdated Record last modified

wso2 api manager UPGRADE

Affected: >= 3.1.0 and < 3.1.0.278 · >= 3.2.0 and < 3.2.0.368 · >= 4.0.0 and < 4.0.0.280 · >= 4.1.0 and < 4.1.0.206 · >= 4.2.0 and < 4.2.0.144 · >= 4.3.0 and < 4.3.0.57

Fixed in: 3.1.0.278, 3.2.0.368, 4.0.0.280, 4.1.0.206, 4.2.0.144, 4.3.0.57

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.278 (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.300 · >= 5.11.0 and < 5.11.0.329 · >= 6.0.0 and < 6.0.0.179 · >= 6.1.0 and < 6.1.0.136

Fixed in: 5.10.0.300, 5.11.0.329, 6.0.0.179, 6.1.0.136

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.300 (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.296

Fixed in: 5.10.0.296

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.296 (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.328

Fixed in: 2.0.0.328

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.328 (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.348

Fixed in: 2.0.0.348

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.348 (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-2024-2374?

api manager: upgrade to 3.1.0.278, 3.2.0.368, 4.0.0.280, 4.1.0.206, 4.2.0.144, 4.3.0.57; identity server: upgrade to 5.10.0.300, 5.11.0.329, 6.0.0.179, 6.1.0.136; identity server as key manager: upgrade to 5.10.0.296. Exact commands for each OS are on this page.

Is CVE-2024-2374 being exploited?

CVE-2024-2374 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-2374 affect?

CVE-2024-2374 affects api manager, identity server, identity server as key manager. Severity is high (CVSS 7.5). The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the resolution of external entities. This omission allows malicious actors to craft XML payloads that exploit the parser's b

How urgent is CVE-2024-2374?

Priority 39/100. High severity; Remotely exploitable, no login, no user action

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

References

← Back to latest CVEs