GHSA-7v28-g2pq-ggg8 — ghost
MEDIUMGHSA-7v28-g2pq-ggg8 is a medium-severity (CVSS 6.6) vulnerability in ghost. A fix is available for ghost — see the affected versions and patch details below.
Ghost vulnerable to remote code execution in locale setting change
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
A vulnerability in an upstream library means an authenticated attacker can abuse locale input to execute arbitrary commands from a file that has previously been uploaded using the file upload functionality in the post editor.
Patches
Fixed in 5.2.3, all 5.x sites should update as soon as possible. Fixed in 4.48.2, all 4.x sites should update as soon as possible.
Workarounds
Patched versions of Ghost add validation to the locale input to prevent execution of arbitrary files. Updating Ghost is the quickest complete solution.
As a workaround, if for any reason you cannot update your Ghost instance, you can block the POST /ghost/api/admin/settings/ endpoint, which will also disable updating settings for your site.
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Credits
- devx00 - https://twitter.com/devx00
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ghost | all versions | 4.48.2npm install ghost@4.48.2 |
| 📦npm | ghost | ≥ 5.0.0&&< 5.2.3 | 5.2.3npm install ghost@5.2.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ghost, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ghost to 4.48.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7v28-g2pq-ggg8 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7v28-g2pq-ggg8 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7v28-g2pq-ggg8. 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-7v28-g2pq-ggg8 in your dependencies?
O3 Security finds GHSA-7v28-g2pq-ggg8 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.