Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-8010: The component accepts XML input through the publisher without disabling external entity resolution

17
Routine
LOW 3.5UPGRADE

CVE-2024-8010 is a low-severity flaw (CVSS 3.5) affecting api manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The component accepts XML input through the publisher without disabling external entity resolution. This allows malicious actors to submit a crafted XML payload that exploits the unescaped external entity references. By leveraging this vulnerability, a malicious actor can read confidential files from the product's file system or access limited HTTP resources reachable via HTTP GET requests to the vulnerable product.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score3.5 (Low)
Attack vectorAdjacent network
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 80%)
CISA exploited listNo
WeaknessCWE-611
Published2026-04-16
Last modified2026-06-17
Publisher (CNA): WSO2 LLC · Vendor: wso2

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

wso2 api manager UPGRADE
Affected: >= 3.2.0 and < 3.2.0.397 · >= 3.2.1 and < 3.2.1.27 · >= 4.0.0 and <= 4.0.0.310 · >= 4.1.0 and < 4.1.0.171 · >= 4.2.0 and < 4.2.0.127 · >= 4.3.0 and < 4.3.0.39
Fixed in: 3.2.0.397, 3.2.1.27, 4.1.0.171, 4.2.0.127, 4.3.0.39
Safe to downgrade to: a release before 3.2.0
1. Check installed version
apt-cache policy api-manager || rpm -q api-manager || api-manager --version
2. UPGRADE to 3.2.0.397 (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.2.0 (Debian / Ubuntu)
apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_3.2.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.2.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.
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-8010?

api manager: upgrade to 3.2.0.397, 3.2.1.27, 4.1.0.171, 4.2.0.127, 4.3.0.39. Exact commands for each OS are on this page.

Is CVE-2024-8010 being exploited?

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

CVE-2024-8010 affects api manager. Severity is low (CVSS 3.5). The component accepts XML input through the publisher without disabling external entity resolution. This allows malicious actors to submit a crafted XML payload that exploits the unescaped external entity references. By leveraging this vul

How urgent is CVE-2024-8010?

Priority 17/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.