How severe is GHSA-7w85-pp86-p4pq?

GHSA-7w85-pp86-p4pq has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7w85-pp86-p4pq?

GHSA-7w85-pp86-p4pq affects the following packages: org.dspace:dspace-xmlui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7w85-pp86-p4pq?

Update org.dspace:dspace-xmlui to 6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7w85-pp86-p4pq is resolved across your whole dependency graph.

How do I detect GHSA-7w85-pp86-p4pq in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.dspace:dspace-xmlui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7w85-pp86-p4pq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7w85-pp86-p4pq?

O3 pinpoints whether GHSA-7w85-pp86-p4pq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7w85-pp86-p4pq actively exploited in the wild?

No public exploit code has been indexed for GHSA-7w85-pp86-p4pq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7w85-pp86-p4pq?

GHSA-7w85-pp86-p4pq has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-7w85-pp86-p4pq published, and has it been updated?

GHSA-7w85-pp86-p4pq was published on August 6, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-7w85-pp86-p4pq

MEDIUM

XMLUI's metadata of withdrawn Items is exposed to anonymous users

Also known asCVE-2022-31190

Published

Aug 6, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk48th percentile+0.42%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.dspace:dspace-xmlui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Metadata on a withdrawn Item is exposed via the XMLUI "mets.xml" object, as long as you know the handle/URL of the withdrawn Item. This vulnerability only impacts the XMLUI.

However, this vulnerability is very low severity as Item metadata does not tend to contain highly secure or sensitive information.

This vulnerability does NOT impact the JSPUI or 7.x.

Patches

Because of the low severity of this security issue, it requires updating to 6.4 to resolve. No patch is available for 5.x or below.

DSpace 6.x:

Fixed in 6.4 via #2451
6.x patch file: https://github.com/DSpace/DSpace/commit/574e25496a40173653ae7d0a49a19ed8e3458606.patch (may be applied manually if an immediate upgrade to 6.4 or above is not possible)

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 as follows:

Download the appropriate patch file to the machine where DSpace is running
From the [dspace-src] folder, apply the patch, e.g. git apply [name-of-file].patch
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 code)
2. Redeploy DSpace, e.g. ant update (This will copy all updated WARs / configs to your installation directory). Depending on your setup you also may need to copy the updated WARs over to your Tomcat webapps folder.
3. Restart Tomcat

Workaround

If there are any withdrawn items which are known to have highly secure information in their metadata, they can be permanently deleted. This will ensure their secure metadata is inaccessible & removed from the system entirely.

References

Discovered & reported by David Cavrenne of Atmire

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.dspace:dspace-xmlui`	≥ 4.0&&< 6.4	6.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.dspace:dspace-xmlui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.dspace:dspace-xmlui to 6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7w85-pp86-p4pq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7w85-pp86-p4pq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7w85-pp86-p4pq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Metadata on a withdrawn Item is exposed via the XMLUI "mets.xml" object, as long as you know the handle/URL of the withdrawn Item. This vulnerability only impacts the XMLUI. However, this vulnerability is very low severity as Item metadata does not tend to contain highly secure or sensitive information. _This vulnerability does NOT impact the JSPUI or 7.x._ ### Patches Because of the low severity of this security issue, it requires updating to 6.4 to resolve. _No patch is available for 5.x or below._ _DSpace 6.x:_ * Fixed in 6.4 via #2451 * 6.x patch file: https://github.com/

O3 Security · Impact-Aware SCA

Is GHSA-7w85-pp86-p4pq in your dependencies?

O3 detects GHSA-7w85-pp86-p4pq across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works