GHSA-2r9r-8fcg-m38g is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in io.goobi.viewer:viewer-core. A fix is available for io.goobi.viewer:viewer-core — see the affected versions and patch details below.
Goobi viewer Core has Cross-Site Scripting Vulnerability in User Nicknames
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2r9r-8fcg-m38g.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-2r9r-8fcg-m38g plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.goobi.viewer:viewer-coreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.goobi.viewer:viewer-core | all versions | 23.03io.goobi.viewer:viewer-core:23.03 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.goobi.viewer:viewer-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2r9r-8fcg-m38g can be triaged on real exposure rather than presence alone.
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
Is GHSA-2r9r-8fcg-m38g in your dependencies?
O3 Security finds GHSA-2r9r-8fcg-m38g across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.