CVE-2025-53621: Dspace api DSpace Is Vulnerable To XML Vulnerability

MODERATE
Advisory Identifier: GHSA-jjwr-5cfh-7xwh
CVSS 6.9
CWE-611
Published
Advisory Summary

CVE-2025-53621 is a MODERATE (CVSS 6.9) dspace is vulnerable to xml vulnerability (CWE-611: Improper Restriction of XML External Entity Reference) affecting Dspace api libraries in the Maven ecosystem. The issue involves dspace is vulnerable to xml external entity injection during archive imports. Remediation is available by upgrading affected packages to version 7.6.4, 8.2, 9.1.

CVE-2025-53621 at a Glance

CVE Identifier CVE-2025-53621
GHSA Identifier GHSA-jjwr-5cfh-7xwh
Severity MODERATE
CVSS v3.1 Base Score 6.9
CWE Classification CWE-611: Improper Restriction of XML External Entity Reference
Affected Product Dspace api
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.9

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

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

How to Fix CVE-2025-53621

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

org.dspace:dspace-api fixed: 7.6.4
<dependency>
    <groupId>org.dspace</groupId>
    <artifactId>dspace-api</artifactId>
    <version>7.6.4</version>
</dependency>
org.dspace:dspace-api fixed: 8.2
<dependency>
    <groupId>org.dspace</groupId>
    <artifactId>dspace-api</artifactId>
    <version>8.2</version>
</dependency>
org.dspace:dspace-api fixed: 9.1
<dependency>
    <groupId>org.dspace</groupId>
    <artifactId>dspace-api</artifactId>
    <version>9.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=org.dspace

How to Check if You Are Affected

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

mvn dependency:tree -Dincludes=org.dspace

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

Note: The mvn dependency:tree -Dincludes=org.dspace 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 Dspace api, 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

### Impact Two related XXE injection possibilities have been discovered, **impacting all versions of DSpace prior to 7.6.4, 8.2 and 9.1**. 1. External entities are not disabled when parsing XML files during import of an archive (in [Simple Archive Format](https://wiki.lyrasis.org/pages/viewpage.action?pageId=104566653)), either from command-line (`./dspace import` command) or from the "Batch Import (Zip)" user interface feature. _(Likely impacts all versions of DSpace 1.x <= 7.6.3, 8.0 <= 8.1, and 9.0)_ 2. External entities are also not explicitly disabled when parsing XML responses from some upstream services (ArXiv, Crossref, OpenAIRE, Creative Commons) used in [import from external sources](https://wiki.lyrasis.org/pages/viewpage.action?pageId=104566672) via the user interface or REST API. _(Impacts all versions of DSpace 7.0 <= 7.6.3, 8.0 <= 8.1 and 9.0)_ An XXE injection in these files may result in a connection being made to an attacker's site or a local path readable by the Tomcat user, with content potentially being injected into a metadata field. In the latter case, this may result in sensitive content disclosure, including retrieving arbitrary files or configurations from the server where DSpace is running or content from remote URLs. The ability to include content from a remote URL could result in a request forgery attack, and disclosure of sensitive information in the response. **The Simple Archive Format (SAF) importer / Batch Import (Zip) is only usable by site administrators** (from user interface / REST API) or system administrators (from command-line). Therefore, to exploit this vulnerability, the malicious payload would have to be provided by an attacker and trusted by an administrator (who would trigger the import). * **The most severe practical impact** is a case where an attacker obtains DSpace administrator credentials and uses the Batch Import feature with a malicious SAF archive to expose sensitive local files readable by the Tomcat user, or secrets and access tokens from an authenticated service via request forgery. * An attacker without administrative credentials might use some other tactic to convince an administrator to import a malicious SAF archive they have supplied. **The Import from External Sources feature has a narrower attack vector**. While this feature is usable by any DSpace Submitter, the malicious payload must be provided *by the external source* (e.g. arXiv, Crossref, OpenAIRE, or Creative Commons). No known method exists for an attacker to inject XXE via content uploads. Instead, the service itself would need to be compromised in such a way that it would inject a malicious payload into its API response. ### Patches The fix is included in DSpace 7.6.4, 8.2 and 9.1. Please upgrade to one of these versions. If you cannot upgrade immediately, it is possible to manually patch your DSpace backend. (No changes are necessary to the frontend.) A pull request exists which can be used to patch systems running DSpace 7.6.x, 8.x or 9.0. This pull request provides central methods to retrieve Java XML, SAX, JAXB XML document builders with safe default settings, including XXE protection. * Pull request for 7.x: https://github.com/DSpace/DSpace/pull/11032 ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/11032.patch)) * Pull request for 8.x: https://github.com/DSpace/DSpace/pull/11034 ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/11034.patch)) * Pull request for 9.0: https://github.com/DSpace/DSpace/pull/11035 ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/11035.patch)) #### Apply the patch to your DSpace If at all possible, we recommend upgrading your DSpace site based on the upgrade instructions. However, if you are unable to do so, you can manually apply the above patches to your DSpace backend as follows: 1. Download the appropriate patch file to the machine where DSpace backend is running 2. From the `[dspace-src]` folder, apply the patch, e.g. `git apply [name-of-file].patch` 3. Now, update your DSpace site (based loosely on the Upgrade instructions). This generally involves three steps: 1. Rebuild DSpace, e.g. `mvn -U clean package` (This will recompile all DSpace backend code) 2. Redeploy DSpace, e.g. `ant update` (This will copy all newly built code to your installation directory). Depending on your setup you also may need to copy the updated "server" webapp over to your Tomcat webapps folder. 3. Restart Tomcat (or runnable JAR) ### Workarounds **Patching the system is the recommended fix.** It is not possible to fully protect your system via workarounds. That said, until you are able to patch your system or upgrade, you can apply these best practices: * Administrators must carefully inspect any SAF archives (they did not construct themselves) before importing. If SAF archives are too large to manually inspect, you should avoid importing them until your site is patched. * As necessary, affected external services can be disabled (see [documentation](https://wiki.lyrasis.org/pages/viewpage.action?pageId=104566672)) to mitigate the ability for a malicious payload to be delivered via external service APIs. ### Credits Discovered & reported by Pablo Picurelli Ortiz (@superpegaso2703) Code fix developed by Kim Shepherd (@kshepherd) of The Library Code ### For more information * [XXE Cheat Sheet / Explanations](https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html) * If you have any questions or comments about this advisory, please contact us at [security@dspace.org](mailto:security@dspace.org)

CVE-2025-53621 Affected Dspace api Versions

3 component(s)
Fixed Versions:
7.6.48.29.1
Product / Package Ecosystem Affected Versions Fixed Version
org.dspace:dspace-api
Maven
< 7.6.4
7.6.4
org.dspace:dspace-api
Maven
≥ 8.0
< 8.2
8.2
org.dspace:dspace-api
Maven
≥ 9.0
< 9.1
9.1

References

Frequently Asked Questions

What is CVE-2025-53621?
CVE-2025-53621 is a security vulnerability in Dspace api involving DSpace is vulnerable to XML External Entity injection during archive imports under CWE-611: Improper Restriction of XML External Entity Reference.
Which Dspace api versions are affected?
Affected versions include releases prior to 7.6.4, 8.2, 9.1 across affected packages: org.dspace:dspace-api.
What version fixes CVE-2025-53621?
Upgrading to 7.6.4, 8.2, 9.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is dspace-api affected?
Yes, org.dspace:dspace-api is affected in releases prior to 7.6.4, 8.2, 9.1. Upgrade your dependency to 7.6.4, 8.2, 9.1 or later.
What is the CVSS score of CVE-2025-53621?
CVE-2025-53621 has a CVSS v3.1 base score of 6.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:L.
What CWE is associated with CVE-2025-53621?
CVE-2025-53621 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-53621?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.dspace'. 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-jjwr-5cfh-7xwh",
  "modified" : "2025-07-15T18:04:53Z",
  "published" : "2025-07-15T18:04:53Z",
  "aliases" : [ "CVE-2025-53621" ],
  "summary" : "DSpace is vulnerable to XML External Entity injection during archive imports ",
  "details" : "### Impact\n\nTwo related XXE injection possibilities have been discovered, **impacting all versions of DSpace prior to 7.6.4, 8.2 and 9.1**.\n\n1. External entities are not disabled when parsing XML files during import of an archive (in [Simple Archive Format](https://wiki.lyrasis.org/pages/viewpage.action?pageId=104566653)), either from command-line (`./dspace import` command) or from the \"Batch Import (Zip)\" user interface feature.  _(Likely impacts all versions of DSpace 1.x <= 7.6.3, 8.0 <= 8.1, and 9.0)_\n2. External entities are also not explicitly disabled when parsing XML responses from some upstream services (ArXiv, Crossref, OpenAIRE, Creative Commons) used in [import from external sources](https://wiki.lyrasis.org/pages/viewpage.action?pageId=104566672) via the user interface or REST API. _(Impacts all versions of DSpace 7.0 <= 7.6.3, 8.0 <= 8.1 and 9.0)_\n\nAn XXE injection in these files may result in a connection being made to an attacker's site or a local path readable by the Tomcat user, with content potentially being injected into a metadata field. In the latter case, this may result in sensitive content disclosure, including retrieving arbitrary files or configurations from the server where DSpace is running or content from remote URLs. The ability to include content from a remote URL could result in a request forgery attack, and disclosure of sensitive information in the  response.\n\n**The Simple Archive Format (SAF) importer / Batch Import (Zip) is only usable by site administrators** (from user interface / REST API) or system administrators (from command-line).  Therefore, to exploit this vulnerability, the malicious payload would have to be provided by an attacker and trusted by an administrator (who would trigger the import).\n* **The most severe practical impact** is a case where an attacker obtains DSpace administrator credentials and uses the Batch Import feature with a malicious SAF archive to expose sensitive local files readable by the Tomcat user, or secrets and access tokens from an authenticated service via request forgery.\n* An attacker without administrative credentials might use some other tactic to convince an administrator to import a malicious SAF archive they have supplied.\n\n**The Import from External Sources feature has a narrower attack vector**.  While this feature is usable by any DSpace Submitter, the malicious payload must be provided *by the external source* (e.g. arXiv, Crossref, OpenAIRE, or Creative Commons).  No known method exists for an attacker to inject XXE via content uploads. Instead, the service itself would need to be compromised in such a way that it would inject a malicious payload into its API response.\n\n### Patches\n\nThe fix is included in DSpace 7.6.4, 8.2 and 9.1. Please upgrade to one of these versions.\n\nIf you cannot upgrade immediately, it is possible to manually patch your DSpace backend. (No changes are necessary to the frontend.)  A pull request exists which can be used to patch systems running DSpace 7.6.x, 8.x or 9.0. This pull request provides central methods to retrieve Java XML, SAX, JAXB XML document builders with safe default settings, including XXE protection.\n* Pull request for 7.x: https://github.com/DSpace/DSpace/pull/11032 ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/11032.patch))\n* Pull request for 8.x: https://github.com/DSpace/DSpace/pull/11034 ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/11034.patch))\n* Pull request for 9.0: https://github.com/DSpace/DSpace/pull/11035 ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/11035.patch))\n\n#### Apply the patch to your DSpace\nIf at all possible, we recommend upgrading your DSpace site based on the upgrade instructions. However, if you are unable to do so, you can manually apply the above patches to your DSpace backend as follows:\n1. Download the appropriate patch file to the machine where DSpace backend is running\n2. From the `[dspace-src]` folder, apply the patch, e.g. `git apply [name-of-file].patch`\n3. Now, update your DSpace site (based loosely on the Upgrade instructions). This generally involves three steps:\n    1. Rebuild DSpace, e.g. `mvn -U clean package`  (This will recompile all DSpace backend code)\n    2. Redeploy DSpace, e.g. `ant update`  (This will copy all newly built code to your installation directory). Depending on your setup you also may need to copy the updated \"server\" webapp over to your Tomcat webapps folder.\n    3. Restart Tomcat (or runnable JAR)\n\n### Workarounds\n**Patching the system is the recommended fix.** It is not possible to fully protect your system via workarounds.\n\nThat said, until you are able to patch your system or upgrade, you can apply these best practices:\n* Administrators must carefully inspect any SAF archives (they did not construct themselves) before importing.  If SAF archives are too large to manually inspect, you should avoid importing them until your site is patched.\n* As necessary, affected external services can be disabled (see [documentation](https://wiki.lyrasis.org/pages/viewpage.action?pageId=104566672)) to mitigate the ability for a malicious payload to be delivered via external service APIs.\n\n\n### Credits\nDiscovered & reported by Pablo Picurelli Ortiz (@superpegaso2703)\nCode fix developed by Kim Shepherd (@kshepherd) of The Library Code\n\n### For more information\n* [XXE Cheat Sheet / Explanations](https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html)\n* If you have any questions or comments about this advisory, please contact us at [security@dspace.org](mailto:security@dspace.org)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.dspace:dspace-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "7.6.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.dspace:dspace-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0"
      }, {
        "fixed" : "8.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.dspace:dspace-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0"
      }, {
        "fixed" : "9.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/security/advisories/GHSA-jjwr-5cfh-7xwh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-53621"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/pull/11032"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/pull/11032.patch"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/pull/11034"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/pull/11034.patch"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/pull/11035"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DSpace/DSpace/pull/11035.patch"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/DSpace/DSpace"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-611" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-07-15T18:04:53Z",
    "nvd_published_at" : "2025-07-15T15:15:25Z"
  }
}