Skip to content
Noroxi
NVD / CVE Program· CNA WSO2

CVE-2024-2374: XML External Entity Injection in Multiple WSO2 Products Allows Arbitrary file read and Denial of Service

CriticalCVSS 9.1 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 product. Additionally, the vulnerability can be exploited to perform denial of service attacks by exhausting server resources through recursive entity expansion or fetching large external resources.

Published
Apr 16, 2026
Updated
Nov 8, 2026
EPSS
0.3% · 32th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.1
CNA · WSO2
7.5
1.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-2374

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
wso2api manager
wso2identity server
wso2identity server as key manager
wso2open banking am
wso2open banking iam

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 WSO2 API Manager

    • before 3.1.0unknown
    • 3.1.0 and later · before 3.1.0.278affected
    • 3.2.0 and later · before 3.2.0.368affected
    • 4.0.0 and later · before 4.0.0.280affected
    • 4.1.0 and later · before 4.1.0.206affected
    • 4.2.0 and later · before 4.2.0.144affected
    • 4.3.0 and later · before 4.3.0.57affected

  • WSO2 WSO2 Identity Server

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.300affected
    • 5.11.0 and later · before 5.11.0.329affected
    • 6.0.0 and later · before 6.0.0.179affected
    • 6.1.0 and later · before 6.1.0.136affected

  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.296affected

  • WSO2 WSO2 Open Banking AM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.328affected

  • WSO2 WSO2 Open Banking IAM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.348affected
Affected versions · NVD (13)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 api manager3.1.0 and later · before 3.1.0.278
  • wso2 api manager3.2.0 and later · before 3.2.0.368
  • wso2 api manager4.0.0 and later · before 4.0.0.280
  • wso2 api manager4.1.0 and later · before 4.1.0.206
  • wso2 api manager4.2.0 and later · before 4.2.0.144
  • wso2 api manager4.3.0 and later · before 4.3.0.57
  • wso2 identity server5.10.0 and later · before 5.10.0.300
  • wso2 identity server5.11.0 and later · before 5.11.0.329
  • wso2 identity server6.0.0 and later · before 6.0.0.179
  • wso2 identity server6.1.0 and later · before 6.1.0.136
  • wso2 identity server as key manager5.10.0 and later · before 5.10.0.296
  • wso2 open banking am2.0.0 and later · before 2.0.0.328
  • wso2 open banking iam2.0.0 and later · before 2.0.0.348

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-29464Certain WSO2 products allow unrestricted file upload with resultant remote code execution.KEV
    99Now
  • CVE-2020-24589The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0 allows XML External Entity injection (XXE) attacks.
    44Plan
  • CVE-2026-2053Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-4867Apr 16, 2026 · Cross-Site Scripting via Developer Portal in WSO2 API Manager Enables UI Modification and Information Retrieval
    21Monitor
  • ← EarlierCVE-2024-8010Apr 16, 2026 · XML External Entity Injection via Publisher in WSO2 API Manager Allows Reading Arbitrary Files
    30Monitor
  • Later →CVE-2025-6024Apr 16, 2026 · Cross-Site Scripting via Authentication Endpoint in Multiple WSO2 Products Allows Redirection to Malicious Websites
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-2905346 days apartAn XML External Entity (XXE) vulnerability in Multiple WSO2 Products
    36Monitor
  • CVE-2024-80100 days apartXML External Entity Injection via Publisher in WSO2 API Manager Allows Reading Arbitrary Files
    30Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-611 · Improper Restriction of XML External Entity Reference

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records