GHSA-rh9f-gr6q-mpc4 is a medium-severity (CVSS 4.9) Cross-site Scripting (XSS) vulnerability in moonshine/moonshine. A fix is available for moonshine/moonshine — see the affected versions and patch details below.
moonshine Stored Cross-Site Scripting Vulnerability in Create Admin
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-rh9f-gr6q-mpc4.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-rh9f-gr6q-mpc4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
moonshine/moonshineReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A Stored Cross-Site Scripting (XSS) vulnerability exists in MoonShine version < 3.12.4, allowing remote attackers to store and execute arbitrary JavaScript by including a malicious HTML payload in the Name parameter when creating a new Admin.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moonshine/moonshine | all versions | 3.12.14composer require moonshine/moonshine:^3.12.14 |
Affected Products
moonshinemoonshineDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moonshine/moonshine, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moonshine/moonshine to 3.12.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rh9f-gr6q-mpc4 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-rh9f-gr6q-mpc4 in your dependencies?
Find it across Packagist, including transitive dependencies.