JavaScript execution via malicious molfiles (XSS)GHSA-2pwh-52h7-7j84
MEDIUMGHSA-2pwh-52h7-7j84 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in de.ipb-halle:molecularfaces. A fix is available for de.ipb-halle:molecularfaces — see the affected versions and patch details below.
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-2pwh-52h7-7j84.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-2pwh-52h7-7j84 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
de.ipb-halle:molecularfacesReal-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
The viewer plugin implementation of <mol:molecule> renders molfile data directly inside a <script> tag without any escaping. Arbitrary JavaScript code can thus be executed in the client browser via crafted molfiles.
Patches
Patched in v0.3.0: Molfile data is now rendered as value of a hidden <input> tag and escaped via JSF's mechanisms.
Workarounds
No workaround available.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | de.ipb-halle:molecularfaces | all versions | 0.3.0de.ipb-halle:molecularfaces:0.3.0 |
Affected Products
molecularfacesipb-halleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.ipb-halle:molecularfaces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update de.ipb-halle:molecularfaces to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pwh-52h7-7j84 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 GHSA-2pwh-52h7-7j84 in your dependencies?
Find it across Maven, including transitive dependencies.