cve.bz

CVE-2025-2905 wso2 api manager

9.1 criticalEPSS 1.3%Fix available

Critical (9.1) in wso2 api manager. EPSS 1.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.wso2.am:am-distribution-parent 2.1.0.

On this page
Due to the improper configuration of XML parser, user-supplied XML is parsed without applying sufficient restrictions, enabling XML External Entity (XXE) resolution in multiple WSO2 Products. A successful XXE attack could allow a remote, unauthenticated attacker to: * Read sensitive files from the server’s filesystem. * Perform denial-of-service (DoS) attacks, which can render the affected service unavailable.

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
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 72nd 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: total, assessed 2025-05-05. 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, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-2905 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-2905?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-2905?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-2025-2905 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 Managerbefore 2.0.0
WSO2 API Manager2.1.0
WSO2 API Manager2.2.0
WSO2 API Manager2.5.0
WSO2 API Manager2.6.0
WSO2 API Manager3.0.0
WSO2 API Manager3.1.0
WSO2 API Managerfrom 4.0.0 before 4.0.0.311
WSO2 API Managerfrom 4.1.0 before 4.1.0.152
WSO2 API Managerfrom 4.2.0 before 4.2.0.122
WSO2 Enterprise Integrator6.0.0
WSO2 Enterprise Integrator6.1.0
WSO2 Enterprise Integrator6.1.1
WSO2 Enterprise Integrator6.2.0
WSO2 Enterprise Integrator6.3.0
WSO2 Enterprise Integrator6.4.0
WSO2 Enterprise Integrator6.5.0
WSO2 Enterprise Integrator6.6.0
WSO2 Enterprise Service Bus4.9.0
WSO2 Enterprise Service Bus5.0.0
WSO2 Micro integrator1.0.0
WSO2 Micro integrator1.1.0
WSO2 Micro integratorfrom 1.2.0 before 1.2.0.162
WSO2 Micro integratorfrom 4.0.0 before 4.0.0.132
WSO2 Micro integratorfrom 4.1.0 before 4.1.0.115
WSO2 Micro integratorfrom 4.2.0 before 4.2.0.112
WSO2 Open Banking AM1.5.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h94w-8qhg-3xmcMavenorg.wso2.am:am-distribution-parent<2.1.02.1.0

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET WEB_SPECIFIC_APPS WSO2 API Manager Blind XML External Entity Injection (CVE-2025-2905) M1 sid 2065716
  • Emerging Threats Open ET WEB_SPECIFIC_APPS WSO2 API Manager Blind XML External Entity Injection (CVE-2025-2905) M2 sid 2065717
  • Emerging Threats Open ET WEB_SPECIFIC_APPS WSO2 API Manager Blind XML External Entity Injection (CVE-2025-2905) M3 sid 2065718

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