GHSA-9fgx-q25h-jxrg is a medium-severity (CVSS 6.8) Cross-site Scripting (XSS) vulnerability in ghost. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-9fgx-q25h-jxrg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
DOM XSS in Theme Preview
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
ghostnpmDescription
Impact
An unused endpoint added during the development of 4.0.0 has left sites vulnerable to untrusted users gaining access to Ghost Admin. Attackers can gain access by getting logged in users to click a link containing malicious code. Users do not need to enter credentials and may not know they've visited a malicious site.
Ghost(Pro) has already been patched. We can find no evidence that the issue was exploited on Ghost(Pro) prior to the patch being added.
Self-hosters are impacted if running Ghost a version between 4.0.0 and 4.3.2. Immediate action should be taken to secure your site - see patches & workarounds below.
Patches
Fixed in 4.3.3, all 4.x sites should upgrade as soon as possible. As the endpoint is unused, the patch simply removes it.
Workarounds
- Log out of Ghost Admin
- Suspend any users who cannot log out
- Block access to
/ghost/preview
Example of how to block access in nginx:
location ~ /ghost/preview {
rewrite ^(\/(.*\/)?ghost\/)(.*)$ $1 redirect;
}
This redirects the endpoint to /ghost/, which mimics the behaviour after the patch is applied.
References
For more information
If you have any questions or comments about this advisory:
- email us at [email protected]
Credits: Paul Gerste, SonarSource (https://www.sonarsource.com/)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ghost | ≥ 4.0.0&&< 4.3.3 | 4.3.3 |
Research 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 ghost. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ghost to 4.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9fgx-q25h-jxrg 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 pinpoints whether GHSA-9fgx-q25h-jxrg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-9fgx-q25h-jxrg. 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-9fgx-q25h-jxrg in your dependencies?
O3 detects GHSA-9fgx-q25h-jxrg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.