dbcve.org
Api ManagerApplication · Wso2

CVE-2020-12719

HIGH · 7.2 CVSS v3.1 Published 2020-05-08
Fix available
A fix is available. Upgrade to after 6.4.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
XXE during an EventPublisher update can occur in Management Console in WSO2 API Manager 3.0.0 and earlier, API Manager Analytics 2.5.0 and earlier, API Microgateway 2.2.0, Enterprise Integrator 6.4.0 and earlier, IS as Key Manager 5.9.0 and earlier, Identity Server 5.9.0 and earlier, and Identity Server Analytics 5.6.0 and earlier.

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

XML External Entity (XXE) injection vulnerability in WSO2 Management Console allows authenticated attackers to inject malicious XML during EventPublisher configuration updates, potentially enabling file disclosure or SSRF attacks.

MitigationUpdate to vendor-patched versions of affected WSO2 products; alternatively, disable XML external entity processing in the application's XML parser configuration.

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 ManagerApplication
Affected:<= 3.0.0
Api Manager AnalyticsApplication
Affected:<= 2.5.0
Api MicrogatewayApplication
Affected:= 2.2.0
Enterprise IntegratorApplication
Affected:<= 6.4.0
Identity ServerApplication
Affected:<= 5.9.0
Identity Server AnalyticsApplication
Affected:<= 5.6.0
Identity Server As Key ManagerApplication
Affected:<= 5.9.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 the installed WSO2 product
    Locate the product by checking the product name in the installation directory, Management Console login page, or process name (e.g., wso2carbon, api-manager, identity-server)
    Affected if The product is one of: API Manager, API Manager Analytics, API Microgateway, Enterprise Integrator, Identity Server, Identity Server Analytics, or Identity Server as Key Manager
  2. Check the installed version number
    Access the Management Console and navigate to 'About' or check the product's version file in the installation directory (typically in the root or conf folder)
    Affected if The version is at or below: 3.0.0 (API Manager), 2.5.0 (API Manager Analytics), 2.2.0 (API Microgateway), 6.4.0 (Enterprise Integrator), 5.9.0 (Identity Server), 5.6.0 (Identity Server Analytics), or 5.9.0 (Identity Server as Key Manager)
  3. Verify access to Management Console EventPublisher configuration
    Log into the Management Console and navigate to Configure > Event Publishers (or the equivalent path for your product version) to determine if the authenticated user role can access EventPublisher configuration
    Affected if The authenticated user has access to create or modify EventPublisher configurations in the Management Console
  4. Confirm XML parser allows external entity processing
    Examine the XML parser configuration files (such as axis2.xml, carbon.xml, or the application's XML parser settings) for settings related to external entity processing (e.g., 'externalEntities' or 'DOCTYPE' processing)
    Affected if The XML parser configuration does not explicitly disable external entity (DTD) processing, leaving XXE parsing enabled

A user is affected if they are running any of the listed WSO2 products at or below the specified versions AND have authenticated access to the Management Console's EventPublisher configuration with an XML parser that allows external entity processing.

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
Upgrade available Upgrade to a release after 6.4.0
Interim mitigation

Update to vendor-patched versions of affected WSO2 products; alternatively, disable XML external entity processing in the application's XML parser configuration.

Fix this in Api Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12719 — 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-2020-12719 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