GHSA-4pvx-fwjj-8gpc: Medium severity npm/ghost vulnerability
Impact
Staff users with the Editor or Super Editor role were able to assign their own role to Author and Contributor users, despite not having permission to assign that role.
Vulnerable versions
This vulnerability is present in Ghost from v0.5.0 up to v6.64.0.
Patches
v6.64.0 contains a fix for this issue.
How to update
For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.
If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.
References
Ghost thanks SecBuddyF of Tencent KeenLab, Santosh Kumar Puppala, Pedro Pinho, and Nhat Anh Vu for disclosing this vulnerability responsibly.
For more information
If you have any questions or comments about this advisory, email us at security@ghost.org.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/ghostto a version that resolves this vulnerability.Fixed in 6.64.0 - Upgrade
Upgrade
Ghostto a version that resolves this vulnerability.Fixed in v6.64.0
Event History
Frequently Asked Questions
Who can exploit this issue?
A staff user who already has the Editor or Super Editor role can exploit it. The issue lets them assign themselves the Author or Contributor role even when they do not have permission to assign that role.
Which Ghost deployments need remediation?
Ghost versions from v0.5.0 through v6.64.0 are affected. Update to v6.64.0, which contains the fix.
How should self-hosted instances be updated?
Docker-based deployments should update their Ghost container using the official Ghost Docker image and documented Docker update procedure. Ghost-CLI deployments should use the documented Ghost-CLI update process.