dbcve.org
Api ManagerApplication · Wso2

CVE-2024-8010

HIGH · 7.5 CVSS v3.1 Published 2026-04-16
Fix available
A fix is available. Upgrade to 3.2.0.397 / 3.2.1.27 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an XML External Entity (XXE) injection vulnerability in the XML publisher component. The component accepts XML input without disabling external entity resolution, allowing attackers to submit crafted XML payloads containing malicious external entity references. This enables reading confidential files from the server's file system via file:// protocol or accessing internal HTTP resources reachable by the vulnerable product.

MitigationDisable external entity resolution and DTD processing in the XML parser configuration, and implement input validation for XML submissions to prevent malicious entity references.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api ManagerApplication
Affected:>= 3.2.0, < 3.2.0.397>= 3.2.1, < 3.2.1.27>= 4.0.0, <= 4.0.0.310>= 4.1.0, < 4.1.0.171>= 4.2.0, < 4.2.0.127>= 4.3.0, < 4.3.0.39

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WSO2 API Manager installation path
    Locate the WSO2 API Manager installation directory, typically found at /opt/wso2am/ or C:\Program Files\WSO2\API Manager\ on Windows. If installed from package manager, check /usr/local/wso2/am/ or the directory where you deployed the product.
    Affected if The installation directory cannot be located or the product is not WSO2 API Manager.
  2. Determine the installed WSO2 API Manager version
    Run the version check command from the product bin directory: on Linux/Mac, execute ./wso2server.sh --version or ./api-manager.sh --version; on Windows, run wso2server.bat --version or check the product-info.txt file in the root installation directory.
    Affected if The installed version falls within any of these ranges: 3.2.0 to 3.2.0.396, 3.2.1 to 3.2.1.26, 4.0.0 to 4.0.0.310, 4.1.0 to 4.1.0.170, 4.2.0 to 4.2.0.126, or 4.3.0 to 4.3.0.38.
  3. Verify if XML Publisher functionality is in use
    Check if the XML Publisher feature is enabled by reviewing the WSO2 API Manager management console under Features or by inspecting the repository/components/plugins directory for xmlpublisher related JAR files. Also check if APIs are being published using XML-based documentation or metadata.
    Affected if The XML Publisher component JAR files exist in the plugins directory and XML-based API publishing or documentation features are actively used.
  4. Inspect XML parser configuration for external entity settings
    Examine the axis2.xml configuration file located in the repository/conf/axis2/ directory. Search for parser configuration settings and verify whether external entity resolution and DTD processing have been explicitly disabled in the XMLInputFactory or XMLStreamReader configurations.
    Affected if The XML parser configuration does not contain settings to disable external entity resolution (such as XMLConstants.ACCESS_EXTERNAL_DTD, XMLConstants.ACCESS_EXTERNAL_SCHEMA, or IS_SUPPORTING_EXTERNAL_ENTITIES set to false).

A user is affected if their WSO2 API Manager version matches any of the affected version ranges AND the XML Publisher component is deployed and processing XML input without proper parser hardening to block external entities.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.0.397 / 3.2.1.27 / 4.1.0.171 or later
Fixed in 3.2.0.3973.2.1.274.1.0.171
Interim mitigation

Disable external entity resolution and DTD processing in the XML parser configuration, and implement input validation for XML submissions to prevent malicious entity references.

Recommended fix High confidence

Upgrade to 3.2.0.397+ (3.2.0.x), 3.2.1.27+ (3.2.1.x), >4.0.0.310 (4.0.0.x), or 4.1.0.171+ (4.1.0.x) depending on your current branch

  1. 1. Identify the currently deployed WSO2 API Manager version using the management console or product documentation
  2. 2. Based on your current major version line, plan upgrade to the fixed release: For 3.2.0.x line upgrade to 3.2.0.397 or later, for 3.2.1.x line upgrade to 3.2.1.27 or later, for 4.0.0.x line upgrade to a version greater than 4.0.0.310, for 4.1.0.x line upgrade to 4.1.0.171 or later
  3. 3. Review WSO2 API Manager upgrade guide for your specific version transition at docs.wso2.com
  4. 4. Create a full backup of the current deployment including database and configuration files
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Perform the upgrade following WSO2's official upgrade procedures
  7. 7. Verify the XML parser configuration disables external entity resolution in the publisher component after upgrade
Caveat Review WSO2 migration guides; minor version upgrades typically have minimal breaking changes but database schema updates may be required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data