CVE-2025-52888: Xunit xml plugin Allure Report Allows Improper XXE Vulnerability

HIGH
Advisory Identifier: GHSA-h7qf-qmf3-85qg
CVSS 7.5
CWE-611
Published
Advisory Summary

CVE-2025-52888 is a HIGH (CVSS 7.5) allure report allows improper xxe vulnerability (CWE-611: Improper Restriction of XML External Entity Reference) affecting Xunit xml plugin libraries in the Maven ecosystem. The issue involves allure report allows improper xxe restriction via documentbuilderfactory. Remediation is available by upgrading affected packages to version 2.34.1.

CVE-2025-52888 at a Glance

CVE Identifier CVE-2025-52888
GHSA Identifier GHSA-h7qf-qmf3-85qg
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-611: Improper Restriction of XML External Entity Reference
Affected Product Xunit xml plugin
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-52888

To remediate this vulnerability, upgrade all affected Xunit xml plugin dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.qameta.allure.plugins:xunit-xml-plugin fixed: 2.34.1
<dependency>
    <groupId>io.qameta.allure.plugins</groupId>
    <artifactId>xunit-xml-plugin</artifactId>
    <version>2.34.1</version>
</dependency>
io.qameta.allure.plugins:junit-xml-plugin fixed: 2.34.1
<dependency>
    <groupId>io.qameta.allure.plugins</groupId>
    <artifactId>junit-xml-plugin</artifactId>
    <version>2.34.1</version>
</dependency>
io.qameta.allure.plugins:trx-plugin fixed: 2.34.1
<dependency>
    <groupId>io.qameta.allure.plugins</groupId>
    <artifactId>trx-plugin</artifactId>
    <version>2.34.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.qameta.allure.plugins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-52888, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.qameta.allure.plugins

Analyze the terminal output to locate any version of Xunit xml plugin in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.34.1), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.qameta.allure.plugins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-611: Improper Restriction of XML External Entity Reference, where the product processes an xml document that can contain xml entities with uris that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. In Xunit xml plugin, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2. The plugin fails to securely configure the XML parser (`DocumentBuilderFactory`) and allows external entity expansion when processing test result .xml files. This allows attackers to read arbitrary files from the file system and potentially trigger server-side request forgery (SSRF). ### Details In `\allure2-main\plugins\xunit-xml-plugin\src\main\java\io\qameta\allure\xunitxml\XunitXmlPlugin.java` the application uses `DocumentBuilderFactory` without disabling DTDs or external entities. By generating a report with a malicious xml file within it, an attacker can perform XXE to leverage SSRF, or to read system files. ### PoC To recreate this vulnerability, you need to install allure for command-line (In my POC I used a Windows 11 Machine). 1. Create a folder called `allure`, and within it, create a malicious XML file. I will attach my SSRF and file reading payloads, however, for the rest of the POC, I will focus on reading system files for better screenshots. ##SSRF (replace webhook link with your own) ![image](https://github.com/user-attachments/assets/a1a9a438-b6f1-4675-973f-a43847a84519) ##Reading System Files ![image](https://github.com/user-attachments/assets/eb0e1e60-1f76-42e7-b68d-2137bed62fe9) 2. Put the malicious .xml file into the `allure` directory created previously 3. Run the following command to run the report `allure generate C:\path\to\directory\allure -o report --clean` 4. To view and confirm the executed payload, run `allure open report` 5. When the report opens, confirm the payload executedby going to `Categories > Product defects > <payload response>` ![image](https://github.com/user-attachments/assets/e7244550-2e9f-4066-b282-86f1eb8cf5e4) ### Impact The explained XXE vulnerability can lead to Arbitrary File Disclosure and Server-Side Request Forgery. This exploitation can also be carried out silently, meaning it can be carried out without user interaction if the tool is automated within an application, and can go undetected with a carefully crafted payload. This could allow a malicious actor to view other source codes which may contain API or product keys, internal application URLs, or other secret items. This makes it an especially high risk when ran within a CI/CD platform.

CVE-2025-52888 Affected Xunit xml plugin Versions

3 component(s)
Fixed Versions:
2.34.1
Product / Package Ecosystem Affected Versions Fixed Version
io.qameta.allure.plugins:xunit-xml-plugin
Maven
< 2.34.1
2.34.1
io.qameta.allure.plugins:junit-xml-plugin
Maven
< 2.34.1
2.34.1
io.qameta.allure.plugins:trx-plugin
Maven
< 2.34.1
2.34.1

References

Frequently Asked Questions

What is CVE-2025-52888?
CVE-2025-52888 is a security vulnerability in Xunit xml plugin involving Allure Report allows Improper XXE Restriction via DocumentBuilderFactory under CWE-611: Improper Restriction of XML External Entity Reference.
Which Xunit xml plugin versions are affected?
Affected versions include releases prior to 2.34.1 across affected packages: io.qameta.allure.plugins:xunit-xml-plugin, io.qameta.allure.plugins:junit-xml-plugin, io.qameta.allure.plugins:trx-plugin.
What version fixes CVE-2025-52888?
Upgrading to 2.34.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is xunit-xml-plugin affected?
Yes, io.qameta.allure.plugins:xunit-xml-plugin is affected in releases prior to 2.34.1. Upgrade your dependency to 2.34.1 or later.
Is junit-xml-plugin affected?
Yes, io.qameta.allure.plugins:junit-xml-plugin is affected in releases prior to 2.34.1. Upgrade your dependency to 2.34.1 or later.
What is the CVSS score of CVE-2025-52888?
CVE-2025-52888 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2025-52888?
CVE-2025-52888 is classified under CWE-611: Improper Restriction of XML External Entity Reference (The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.).
How can I check Maven dependencies for CVE-2025-52888?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.qameta.allure.plugins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h7qf-qmf3-85qg",
  "modified" : "2025-06-25T14:14:09Z",
  "published" : "2025-06-25T14:14:09Z",
  "aliases" : [ "CVE-2025-52888" ],
  "summary" : "Allure Report allows Improper XXE Restriction via DocumentBuilderFactory",
  "details" : "### Summary\nA critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2. The plugin fails to securely configure the XML parser (`DocumentBuilderFactory`) and allows external entity expansion when processing test result .xml files. This allows attackers to read arbitrary files from the file system and potentially trigger server-side request forgery (SSRF).\n\n### Details\nIn `\\allure2-main\\plugins\\xunit-xml-plugin\\src\\main\\java\\io\\qameta\\allure\\xunitxml\\XunitXmlPlugin.java` the application uses `DocumentBuilderFactory` without disabling DTDs or external entities. By generating a report with a malicious xml file within it, an attacker can perform XXE to leverage SSRF, or to read system files.\n\n### PoC\nTo recreate this vulnerability, you need to install allure for command-line (In my POC I used a Windows 11 Machine). \n\n1. Create a folder called `allure`, and within it, create a malicious XML file. I will attach my SSRF and file reading payloads, however, for the rest of the POC, I will focus on reading system files for better screenshots.\n##SSRF (replace webhook link with your own)\n![image](https://github.com/user-attachments/assets/a1a9a438-b6f1-4675-973f-a43847a84519)\n\n##Reading System Files\n![image](https://github.com/user-attachments/assets/eb0e1e60-1f76-42e7-b68d-2137bed62fe9)\n\n2. Put the malicious .xml file into the `allure` directory created previously\n3. Run the following command to run the report `allure generate C:\\path\\to\\directory\\allure -o report --clean`\n4. To view and confirm the executed payload, run `allure open report`\n5. When the report opens, confirm the payload executedby going to `Categories > Product defects > <payload response>`\n![image](https://github.com/user-attachments/assets/e7244550-2e9f-4066-b282-86f1eb8cf5e4)\n\n\n\n### Impact\nThe explained XXE vulnerability can lead to Arbitrary File Disclosure and Server-Side Request Forgery. This exploitation can also be carried out silently, meaning it can be carried out without user interaction if the tool is automated within an application, and can go undetected with a carefully crafted payload. This could allow a malicious actor to view other source codes which may contain API or product keys, internal application URLs, or other secret items. This makes it an especially high risk when ran within a CI/CD platform.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.qameta.allure.plugins:xunit-xml-plugin"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.34.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.34.0"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.qameta.allure.plugins:junit-xml-plugin"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.34.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.34.0"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.qameta.allure.plugins:trx-plugin"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.34.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.34.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/allure-framework/allure2/security/advisories/GHSA-h7qf-qmf3-85qg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-52888"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/allure-framework/allure2/commit/cbcb33719851ff70adce85d38e15d20fc58d4eb7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/allure-framework/allure2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-611" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-06-25T14:14:09Z",
    "nvd_published_at" : "2025-06-24T20:15:26Z"
  }
}