GHSA-rjhx-c9qh-qh8f is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.glassfish:javax.faces. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.glassfish:javax.faces — see the affected versions and patch details below.
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
org.glassfish:javax.faces☕org.glassfish:jakarta.facesReal-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
faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and Mojarra JavaServer Faces before 2.2.20, allows Reflected XSS because a client window field is mishandled.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.glassfish:javax.faces | all versions | 2.2.20org.glassfish:javax.faces:2.2.20 |
| ☕Maven | org.glassfish:jakarta.faces | all versions | 2.3.10org.glassfish:jakarta.faces:2.3.10 |
Affected Products
mojarraeclipseapplication testing suiteoraclebanking enterprise product manufacturingoraclecommunications diameter signaling routeroraclecommunications network integrityoraclecommunications unified inventory managementoracleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.glassfish:javax.faces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.glassfish:javax.faces to 2.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rjhx-c9qh-qh8f 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-rjhx-c9qh-qh8f in your dependencies?
Find it across Maven, including transitive dependencies.