WSO2 Enterprise Integrator: Improper Restriction of XML External Entity Reference
CVE-2025-10713 is a critical-severity improper restriction of XML external entity reference vulnerability in WSO2 Enterprise Integrator from WSO2, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 6.6.0.223 as the first without the flaw, so updating WSO2 Enterprise Integrator to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update WSO2 Enterprise Integrator to 6.6.0.223 or a later version.
- Update WSO2 API Control Plane to 4.5.0.27 or a later version.
- Update WSO2 Universal Gateway to 4.5.0.25 or a later version.
- Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WSO2 | WSO2 Enterprise Integrator | 6.6.0 up to, but not including, 6.6.0.223 | 6.6.0.223 |
| WSO2 | WSO2 API Control Plane | 4.5.0 up to, but not including, 4.5.0.27 | 4.5.0.27 |
| WSO2 | WSO2 Universal Gateway | 4.5.0 up to, but not including, 4.5.0.25 | 4.5.0.25 |
| WSO2 | WSO2 Traffic Manager | 4.5.0 up to, but not including, 4.5.0.25 | 4.5.0.25 |
| WSO2 | WSO2 API Manager | 3.1.0 up to, but not including, 3.1.0.344; 3.2.0 up to, but not including, 3.2.0.445; 3.2.1 up to, but not including, 3.2.1.65; 4.0.0 up to, but not including, 4.0.0.365; 4.1.0 up to, but not including, 4.1.0.227; 4.2.0 up to, but not including, 4.2.0.167; 4.3.0 up to, but not including, 4.3.0.79; 4.4.0 up to, but not including, 4.4.0.43; and 1 more ranges | 3.1.0.344, 3.2.0.445, 3.2.1.65, 4.0.0.365, 4.1.0.227, 4.2.0.167 |
| WSO2 | WSO2 Identity Server | 5.10.0 up to, but not including, 5.10.0.373; 5.11.0 up to, but not including, 5.11.0.417; 7.1.0 up to, but not including, 7.1.0.29 | 5.10.0.373, 5.11.0.417, 7.1.0.29 |
| WSO2 | WSO2 Open Banking IAM | 2.0.0 up to, but not including, 2.0.0.413 | 2.0.0.413 |
| WSO2 | WSO2 Open Banking AM | 2.0.0 up to, but not including, 2.0.0.393 | 2.0.0.393 |
| WSO2 | WSO2 Identity Server as Key Manager | 5.10.0 up to, but not including, 5.10.0.363 | 5.10.0.363 |
| WSO2 | org.wso2.carbon.mediation:org.wso2.carbon.localentry | 4.7.30 up to, but not including, 4.7.30.46; 4.7.61 up to, but not including, 4.7.61.61; 4.7.99 up to, but not including, 4.7.99.303; 4.7.131 up to, but not including, 4.7.131.21; 4.7.175 up to, but not including, 4.7.175.29; 4.7.188 up to, but not including, 4.7.188.11; 4.7.204 up to, but not including, 4.7.204.12; 4.7.221 up to, but not including, 4.7.221.6; and 1 more ranges | 4.7.30.46, 4.7.61.61, 4.7.99.303, 4.7.131.21, 4.7.175.29, 4.7.188.11 |
| WSO2 | API Control Plane | 4.5.0 | Not stated |
| WSO2 | API Manager | 3.1.0; 3.2.0; 3.2.1; 4.0.0; 4.1.0; 4.2.0; 4.3.0; 4.4.0; and 1 more ranges | Not stated |
| WSO2 | Enterprise Integrator | 6.6.0 | Not stated |
| WSO2 | Identity Server | 5.10.0; 5.11.0; 7.1.0 | Not stated |
| WSO2 | Open Banking Am | 2.0.0 | Not stated |
| WSO2 | Open Banking Iam | 2.0.0 | Not stated |
| WSO2 | Traffic Manager | 4.5.0 | Not stated |
| WSO2 | Universal Gateway | 4.5.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.5 | Medium | CNA |
| CVSS 3.1 | 9.1 | Critical | NVD |
Official description
An XML External Entity (XXE) vulnerability exists in multiple WSO2 products due to improper configuration of the XML parser. The application parses user-supplied XML without applying sufficient restrictions, allowing resolution of external entities. A successful attack could enable a remote, unauthenticated attacker to read sensitive files from the server's filesystem or perform denial-of-service (DoS) attacks that render affected services unavailable.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Restriction of XML External Entity Reference
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
How developers prevent this class of flaw
- Many XML parsers and validators can be configured to disable external entity expansion.
More Improper Restriction of XML External Entity Reference vulnerabilities (CWE-611)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in WSO2 Enterprise Integrator
- 9.1 Critical severity
- 7.5 High severity
- 8.8 High severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
Recent Improper Restriction of XML External Entity Reference vulnerabilities
- 9.1 Critical severity
- 7.1 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.