CVE-2025-2905

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.

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.

An XML External Entity (XXE) vulnerability exists in the gateway component of WSO2 API Manager due to insufficient validation of XML input in crafted URL paths. User-supplied XML is parsed without appropriate restrictions, enabling external entity resolution.

This vulnerability can be exploited by an unauthenticated remote attacker to read files from the server’s filesystem or perform denial-of-service (DoS) attacks.

• On systems running JDK 7 or early JDK 8, full file contents may be exposed.

• On later versions of JDK 8 and newer, only the first line of a file may be read, due to improvements in XML parser behavior.

• DoS attacks such as "Billion Laughs" payloads can cause service disruption.

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.

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.

An XML External Entity (XXE) vulnerability exists in the gateway component of WSO2 API Manager due to insufficient validation of XML input in crafted URL paths. User-supplied XML is parsed without appropriate restrictions, enabling external entity resolution.

This vulnerability can be exploited by an unauthenticated remote attacker to read files from the server’s filesystem or perform denial-of-service (DoS) attacks.

• On systems running JDK 7 or early JDK 8, full file contents may be exposed.

• On later versions of JDK 8 and newer, only the first line of a file may be read, due to improvements in XML parser behavior.

• DoS attacks such as "Billion Laughs" payloads can cause service disruption.