Ghost vulnerabilities

Ghost, a Node.js content management system, has a vulnerability in versions 5.121.0 through 5.130.5 and 6.0.0 through 6.10.3. The flaw in Staff Token authentication handling allows access to certain endpoints that were intended to be accessible only via Staff Session authentication. External systems authenticated with Staff Tokens for Admin/Owner-role users could access these endpoints.

Ghost is a Node.js content management system. In versions 5.105.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost's 2FA mechanism allows staff users to skip email 2FA. This issue has been patched in versions 5.130.6 and 6.11.0.

A vulnerability in Ghost Foundation Ghost 5.x allows authenticated Author-role users to delete posts owned by others. The permission check is missing a branch, allowing deletion.

Ghost from 4.9.0 until 6.54.1 had an input validation issue that allowed any staff user to create a post with content in feature_image_caption that could be used to hijack another staff user's Ghost Admin session, resulting in privilege escalation. This issue is fixed in 6.54.1.

Ghost from 6.26.0 until 6.54.1 had a validation issue that allowed some functionality, such as Webmentions, to be abused by an unauthenticated user to make limited HTTP requests to hosts in the Ghost server's internal network. A successful attack would not result in any response data being returned. This vulnerability is fixed in 6.54.1.

Ghost Admin from 2.2.0 to 6.54.1 did not invalidate existing sessions on login, which could have allowed session fixation attacks. Successful exploitation would have required another vulnerability on the same domain.

Ghost is a Node.js content management system. From 0.10.0 until 6.54.1, a vulnerability in custom themes allowed a staff user to write files outside of the uploads directory. This could be used to alter the behavior of the installation through custom theme upload path traversal in LocalStorageBase and theme storage name handling.

Ghost is a Node.js content management system. From 1.20.1 until 6.54.1, an Administrator-level user could remotely overwrite certain files on the filesystem through the database backup filename, leading to integrity and availability issues. The database export endpoint failed to reject path separators in the caller-supplied filename. This issue is fixed in version 6.54.1.

Ghost is a Node.js content management system. From 0.10.0 until 6.54.1, a Server-Side Request Forgery in Ghost Admin image fetching allowed any staff-level user to perform a blind HTTP GET request against internal hosts. No output was returned, but this could have been used to probe open ports on internal hosts. This issue is fixed in version 6.54.1.

Ghost is a Node.js content management system. Prior to version 6.54.1, any staff-level user was able to leak the hashed passwords of other staff users through the Ghost Admin API. An offline password-guessing attack against the hashes could lead to account takeover if successful, but Device Verification should have prevented an attacker from logging in with a recovered password. Depending on the database used, leaked hashes may not have had the correct casing for all characters, increasing the difficulty of a password-guessing attack.

Ghost is a Node.js content management system. From version 4.22.0 until 6.54.1, a missing validation check allowed users to redeem subscription offers that were no longer active. This issue is fixed in version 6.54.1.

Ghost is a Node.js content management system. From 5.26.0 until 6.54.1, the Universal Import feature in Ghost Admin failed to properly sanitize imported content resulting in XSS in post content. This issue is fixed in version 6.54.1.

Ghost, a Node.js content management system, from version 6.27.0 before 6.44.0 had a vulnerability in the public donation checkout flow. An unauthenticated attacker could control donation checkout metadata and obtain full paid gift memberships for a minimal payment.