GHSA-v6q3-xqxm-6f5v: High severity npm/ghost vulnerability
Impact
Staff users with permission to view staff invites were able to discover the secret token of pending invites, including invites for roles with higher privileges than their own. This could allow a staff user to escalate their privileges by accepting a pending invite.
Vulnerable versions
This vulnerability is present in Ghost from v4.39.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 CoryRoo, 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 6.64.0
Event History
Frequently Asked Questions
Who can exploit this issue?
A staff user who has permission to view staff invites can exploit it. The user may use a discovered token from a pending invite for a role with higher privileges than their own.
What access and conditions are required for exploitation?
The attacker must already have a staff account with permission to view staff invites, and there must be a pending invite whose secret token they can discover. Exploitation involves accepting that pending invite to obtain the higher-privileged role.
Which deployments are affected and what version fixes it?
Ghost versions from 4.39.0 up to 6.64.0 are affected. Version 6.64.0 contains the fix.
What can be done if an immediate update is not possible?
Limit the ability to view staff invites to only trusted staff users, and review pending invites, particularly those for privileged roles. Removing unnecessary pending privileged invites reduces the opportunity to use a disclosed invite token.