dbcve.org
Api ManagerApplication · Wso2

CVE-2020-13226

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-20
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
WSO2 API Manager 3.0.0 does not properly restrict outbound network access from a Publisher node, opening up the possibility of SSRF to this node's entire intranet.

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

WSO2 API Manager 3.0.0 Publisher nodes lack proper outbound network access restrictions, enabling Server-Side Request Forgery (SSRF). Attackers can leverage the compromised Publisher node to make arbitrary HTTP requests to internal intranet resources, potentially accessing sensitive internal services, infrastructure, or cloud metadata endpoints.

MitigationImplement strict outbound network access controls on Publisher nodes by configuring WSO2 transport restrictions, deploying network segmentation/firewall rules to block unauthorized outbound connections, and validating all external requests through allowlist-based URL validation.

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

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm WSO2 API Manager version
    Check the product version by inspecting the release.info file in the installation root directory, or by viewing the product version in the Management Console under About > Product Information.
    Affected if The installed version is exactly 3.0.0 (no patches applied).
  2. Identify if this is a Publisher node
    Check the deployment.toml file in the repository/conf directory for the node type configuration, or inspect the current deployment pattern in a clustered setup. Publisher nodes typically have the 'Publisher' profile enabled.
    Affected if This is a Publisher node in a WSO2 API Manager 3.0.0 deployment.
  3. Inspect outbound transport configuration
    Examine the transport.xml file in repository/conf/axis2/ for outbound HTTP/HTTPS transport sender configurations. Look for any unrestricted http/https transport senders without IP range restrictions or block lists.
    Affected if Outbound HTTP transport is enabled without IP/hostname restrictions or allowlisting.
  4. Check for transport-level network restrictions
    Review the carbon.xml file in repository/conf/ for TransportLimitations or network restriction settings. Also check repository/conf/api-manager.xml for any URL validation configurations.
    Affected if No outbound network restrictions are configured in carbon.xml or no URL allowlist validation exists in api-manager.xml.

You are affected if you are running WSO2 API Manager 3.0.0 as a Publisher node with unrestricted outbound HTTP access and no transport-level network restrictions configured.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict outbound network access controls on Publisher nodes by configuring WSO2 transport restrictions, deploying network segmentation/firewall rules to block unauthorized outbound connections, and validating all external requests through allowlist-based URL validation.

Recommended fix Moderate confidence

WSO2 API Manager 3.0.1 or later (e.g., 3.1.0, 3.2.0)

  1. 1. Download WSO2 API Manager 3.0.1 or later from the official WSO2 repository
  2. 2. Back up your current API Manager 3.0.0 configuration and database
  3. 3. Stop the WSO2 API Manager 3.0.0 services
  4. 4. Install WSO2 API Manager 3.0.1 or later
  5. 5. Restore your configuration to the new installation
  6. 6. Start the upgraded API Manager services
  7. 7. Verify that the Publisher node SSRF vulnerability is resolved by testing outbound network restrictions
Caveat Review release notes for any configuration or API compatibility changes between 3.0.0 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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