How severe is GHSA-2r9r-8fcg-m38g?

GHSA-2r9r-8fcg-m38g has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2r9r-8fcg-m38g?

GHSA-2r9r-8fcg-m38g affects the following packages: io.goobi.viewer:viewer-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2r9r-8fcg-m38g?

Update io.goobi.viewer:viewer-core to 23.03 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2r9r-8fcg-m38g is resolved across your whole dependency graph.

How do I detect GHSA-2r9r-8fcg-m38g in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.goobi.viewer:viewer-core. 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-2r9r-8fcg-m38g 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-2r9r-8fcg-m38g?

O3 pinpoints whether GHSA-2r9r-8fcg-m38g 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-2r9r-8fcg-m38g actively exploited in the wild?

No public exploit code has been indexed for GHSA-2r9r-8fcg-m38g 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-2r9r-8fcg-m38g?

GHSA-2r9r-8fcg-m38g has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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-2r9r-8fcg-m38g published, and has it been updated?

GHSA-2r9r-8fcg-m38g was published on April 7, 2023 and was last updated on November 8, 2023. 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-2r9r-8fcg-m38g

MEDIUM

Goobi viewer Core has Cross-Site Scripting Vulnerability in User Nicknames

Also known asCVE-2023-29016

Published

Apr 7, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk35th percentile-0.40%

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

☕io.goobi.viewer:viewer-core

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

A cross-site scripting vulnerability has been identified in Goobi viewer core when using nicknames. An attacker could create a user account and enter malicious scripts into their profile's nickname, resulting in the execution in the user's browser when displaying the nickname on certain pages.

Patches

The vulnerability has been fixed in version 23.03

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	`io.goobi.viewer:viewer-core`	all versions	23.03

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.goobi.viewer:viewer-core. 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 io.goobi.viewer:viewer-core to 23.03 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2r9r-8fcg-m38g 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-2r9r-8fcg-m38g 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-2r9r-8fcg-m38g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A cross-site scripting vulnerability has been identified in Goobi viewer core when using nicknames. An attacker could create a user account and enter malicious scripts into their profile's nickname, resulting in the execution in the user's browser when displaying the nickname on certain pages. ### Patches The vulnerability has been fixed in version 23.03 If you have any questions or comments about this advisory: * Email us at [[email protected]](mailto:[email protected])

O3 Security · Impact-Aware SCA

Is GHSA-2r9r-8fcg-m38g in your dependencies?

O3 detects GHSA-2r9r-8fcg-m38g 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