dbcve.org
Api Control PlaneApplication · Wso2

CVE-2025-10713

CRITICAL · 9.1 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an XML External Entity (XXE) vulnerability in multiple WSO2 products where the XML parser is improperly configured, allowing external entity resolution. An unauthenticated attacker can craft malicious XML to read sensitive files from the server filesystem or cause denial of service.

MitigationConfigure the XML parser to disable external entity resolution and apply proper input validation restrictions to prevent XXE attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api Control PlaneApplication
Affected:= 4.5.0
Api ManagerApplication
Affected:= 3.1.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0
Enterprise IntegratorApplication
Affected:= 6.6.0
Identity ServerApplication
Affected:= 5.10.0= 5.11.0= 7.1.0
Open Banking AmApplication
Affected:= 2.0.0
Open Banking IamApplication
Affected:= 2.0.0
Traffic ManagerApplication
Affected:= 4.5.0
Universal GatewayApplication
Affected:= 4.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WSO2 product and version
    Access the WSO2 management console or welcome page. The version is typically displayed on the landing page or can be found in the product's release.info file in the installation directory.
    Affected if The installed version matches any of the following: API Control Plane 4.5.0; 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, or 4.5.0; Enterprise Integrator 6.6.0; Identity Server 5.10.0, 5.11.0, or 7.1.0; Open Banking AM 2.0.0; Open Banking IAM 2.0.0; Traffic Manager 4.5.0; or U
  2. Locate XML parser configuration files
    In the WSO2 installation directory, examine the axis2.xml file (typically in the conf directory) and any custom XML parser configuration files. Look for XMLInputFactory or XMLStreamReader settings.
    Affected if The XML parser configuration contains settings that allow external entity resolution, such as XMLConstants.ACCESS_EXTERNAL_DTD or XMLConstants.ACCESS_EXTERNAL_SCHEMA set to allow external references, or missing property disables for external entities.
  3. Check for XML endpoint exposure
    Identify endpoints in the WSO2 product that accept XML input. These may include SOAP services, WSDL endpoints, or any API endpoints that process XML payloads. Use the management console or examine the deployment descriptors.
    Affected if The product exposes endpoints that accept unvalidated XML input without proper XXE protections applied at the parser level.

You are affected if your WSO2 product version matches one of the listed versions AND the XML parser is configured to allow external entity resolution, allowing unauthenticated attackers to potentially read sensitive files or cause denial of service through malicious XML.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the XML parser to disable external entity resolution and apply proper input validation restrictions to prevent XXE attacks.

Fix this in Api Control Plane Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,340
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data