cve.bz

CVE-2024-2374 wso2

9.1 criticalEPSS 0.4%

Critical (9.1) in wso2. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-04-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-611 Improper Restriction of XML External Entity Reference
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-2374 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-2374?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-2374?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-2374 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
WSO2 API Managerfrom 3.1.0 before 3.1.0.278
WSO2 API Managerfrom 3.2.0 before 3.2.0.368
WSO2 API Managerfrom 4.0.0 before 4.0.0.280
WSO2 API Managerfrom 4.1.0 before 4.1.0.206
WSO2 API Managerfrom 4.2.0 before 4.2.0.144
WSO2 API Managerfrom 4.3.0 before 4.3.0.57
WSO2 Identity Serverfrom 5.10.0 before 5.10.0.300
WSO2 Identity Serverfrom 5.11.0 before 5.11.0.329
WSO2 Identity Serverfrom 6.0.0 before 6.0.0.179
WSO2 Identity Serverfrom 6.1.0 before 6.1.0.136
WSO2 Open Banking AMfrom 2.0.0 before 2.0.0.328
WSO2 Open Banking IAMfrom 2.0.0 before 2.0.0.348
WSO2 Identity Server as Key Managerfrom 5.10.0 before 5.10.0.296

Attack patterns (CAPEC)

  • CAPEC-221 Data Serialization External Entities Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON