CVE-2025-10713: XML External Entity (XXE) Vulnerability in Multiple WSO2 Products Due to Improper XML Parser Configuration
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.45% (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 the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 9.1.
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
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.
- Published
- Nov 5, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-611
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.1
- CNA · WSO2
- 6.5
- 2.6 point gap
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api control plane | cpe:2.3:a:wso2:api_control_plane |
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | enterprise integrator | cpe:2.3:a:wso2:enterprise_integrator |
| wso2 | identity server | cpe:2.3:a:wso2:identity_server |
| wso2 | open banking am | cpe:2.3:a:wso2:open_banking_am |
| wso2 | open banking iam | cpe:2.3:a:wso2:open_banking_iam |
| wso2 | traffic manager | cpe:2.3:a:wso2:traffic_manager |
| wso2 | universal gateway | cpe:2.3:a:wso2:universal_gateway |
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 org.wso2.carbon.mediation:org.wso2.carbon.localentry
- 4.7.30 and later · before 4.7.30.46affected
- 4.7.61 and later · before 4.7.61.61affected
- 4.7.99 and later · before 4.7.99.303affected
- 4.7.131 and later · before 4.7.131.21affected
- 4.7.175 and later · before 4.7.175.29affected
- 4.7.188 and later · before 4.7.188.11affected
- 4.7.204 and later · before 4.7.204.12affected
- 4.7.221 and later · before 4.7.221.6affected
- 4.7.245 and later · before 4.7.245.6affected
- 4.7.259 and laternot affected
WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.27affected
WSO2 WSO2 API Manager
- before 3.1.0unknown
- 3.1.0 and later · before 3.1.0.344affected
- 3.2.0 and later · before 3.2.0.445affected
- 3.2.1 and later · before 3.2.1.65affected
- 4.0.0 and later · before 4.0.0.365affected
- 4.1.0 and later · before 4.1.0.227affected
- 4.2.0 and later · before 4.2.0.167affected
- 4.3.0 and later · before 4.3.0.79affected
- 4.4.0 and later · before 4.4.0.43affected
- 4.5.0 and later · before 4.5.0.26affected
WSO2 WSO2 Enterprise Integrator
- before 6.6.0unknown
- 6.6.0 and later · before 6.6.0.223affected
WSO2 WSO2 Identity Server
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.373affected
- 5.11.0 and later · before 5.11.0.417affected
- 7.1.0 and later · before 7.1.0.29affected
WSO2 WSO2 Identity Server as Key Manager
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.363affected
WSO2 WSO2 Open Banking AM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.393affected
WSO2 WSO2 Open Banking IAM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.413affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.25affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.25affected
Affected versions · NVD (18)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api control plane4.5.0
- wso2 api manager3.1.0
- wso2 api manager3.2.0
- wso2 api manager3.2.1
- wso2 api manager4.0.0
- wso2 api manager4.1.0
- wso2 api manager4.2.0
- wso2 api manager4.3.0
- wso2 api manager4.4.0
- wso2 api manager4.5.0
- wso2 enterprise integrator6.6.0
- wso2 identity server5.10.0
- wso2 identity server5.11.0
- wso2 identity server7.1.0
- wso2 open banking am2.0.0
- wso2 open banking iam2.0.0
- wso2 traffic manager4.5.0
- wso2 universal gateway4.5.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.wso2.carbon.mediation:org.wso2.carbon.localentry | from 0 | — |
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV77This week
- CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover39Monitor
- CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-5605Oct 24, 2025 · Authentication Bypass via URI Manipulation in Multiple WSO2 Products' Management Console Leading to Partial Information Disclosure21Monitor
- ← EarlierCVE-2025-3125Nov 5, 2025 · Authenticated Arbitrary File Upload in Multiple WSO2 Products via CarbonAppUploader Admin Service Leading to Remote Code Execution28Monitor
- Later →CVE-2025-10907Nov 5, 2025 · Authenticated Arbitrary File Upload in Multiple WSO2 Products via SOAP Admin Services Leading to Remote Code Execution28Monitor
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- crnkovićreporter
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · 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 ReferenceCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.