Skip to content
Noroxi
NVD / CVE Program· CNA WSO2

CVE-2025-2905: An XML External Entity (XXE) vulnerability in Multiple WSO2 Products

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: 1.2% (FIRST EPSS); higher than 70.2% of all records.
  • 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 CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: org.wso2.am:am-distribution-parent (Maven) 2.1.0.

Low priority for now. Upgrade to org.wso2.am:am-distribution-parent (Maven) 2.1.0 or later.

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

Due to the improper configuration of XML parser, user-supplied XML is parsed without applying sufficient restrictions, enabling XML External Entity (XXE) resolution in multiple WSO2 Products. A successful XXE attack could allow a remote, unauthenticated attacker to: * Read sensitive files from the server’s filesystem. * Perform denial-of-service (DoS) attacks, which can render the affected service unavailable.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
May 5, 2025
Updated
Jun 17, 2026
EPSS
1.2% · 70th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · WSO2
9.1
NVD has not scored this yet; the score shown is the CNA’s.

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
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-2905

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
wso2api manager

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 api managerup to 2.0.0 inclusive

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 WSO2 API Manager

    • 2.1.0, 2.2.0, 2.5.0, 2.6.0, 3.0.0, 3.1.0affected
    • before 2.0.0affected
    • 4.0.0 and later · before 4.0.0.311affected
    • 4.1.0 and later · before 4.1.0.152affected
    • 4.2.0 and later · before 4.2.0.122affected

  • WSO2 WSO2 Enterprise Integrator

    • 6.0.0, 6.1.0, 6.1.1, 6.2.0, 6.3.0, 6.4.0, 6.5.0, 6.6.0affected
    • before 6.0.0unknown

  • WSO2 WSO2 Enterprise Service Bus

    • 4.9.0, 5.0.0affected
    • before 4.9.0unknown

  • WSO2 WSO2 Micro integrator

    • 1.0.0, 1.1.0affected
    • before 1.0.0unknown
    • 1.2.0 and later · before 1.2.0.162affected
    • 4.0.0 and later · before 4.0.0.132affected
    • 4.1.0 and later · before 4.1.0.115affected
    • 4.2.0 and later · before 4.2.0.112affected

  • WSO2 WSO2 Open Banking AM

    • 1.5.0affected
    • before 1.5.0unknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.wso2.am:am-distribution-parentbefore 2.1.02.1.0

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-29464Certain WSO2 products allow unrestricted file upload with resultant remote code execution.KEV
    99Now
  • CVE-2020-24589The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0 allows XML External Entity injection (XXE) attacks.
    44Plan
  • CVE-2026-2053Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-2321Feb 27, 2025 · Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token
    22Monitor
  • ← EarlierCVE-2024-5848Feb 27, 2025 · Reflected Cross-Site Scripting (XSS) in Multiple WSO2 Products Due to Improper Input Validation
    24Monitor
  • Later →CVE-2024-6914May 22, 2025 · Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.wso2.am:am-distribution-parent2.1.0Package registry (OSV)

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-2374346 days apartXML External Entity Injection in Multiple WSO2 Products Allows Arbitrary file read and Denial of Service
    36Monitor
  • CVE-2024-8010346 days apartXML External Entity Injection via Publisher in WSO2 API Manager Allows Reading Arbitrary Files
    30Monitor
  • CVE-2023-6836507 days apartMultiple WSO2 products have been identified as vulnerable due to an XML External Entity (XXE) attack abuses a widely available but rarely us
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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 Reference

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records