CVE-2023-29015 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 Comments
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 CVE-2023-29015.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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
The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. A cross-site scripting vulnerability has been identified in the user comment feature of Goobi viewer core prior to version 23.03. An attacker could create a specially crafted comment, resulting in the execution of malicious script code in the user's browser when displaying the comment. The vulnerability has been fixed in version 23.03.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.goobi.viewer:viewer-core | all versions | 23.03io.goobi.viewer:viewer-core:23.03 |
Affected Products
goobi viewer coreintrandaDetection & 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 CVE-2023-29015 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-29015 in your dependencies?
Find it across Maven, including transitive dependencies.