Skip to content

GHSA-7mpp-r37j-x5wh BIT-ghost-2026-70594 CVE-2026-70594

Ghost: Session Fixation in Ghost Admin

Medium npm
Severity
6.7 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.24%
Chance of exploitation in the next 30 days. Higher than 15.64% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-384 Session Fixation
Fix
6.54.1
Upgrade ghost to this version or later

Description

Impact

Ghost Admin did not invalidate existing sessions on login which could have allowed for session fixation attacks. Successful exploitation would have required another vulnerability on the same domain where Ghost Admin was hosted.

Vulnerable versions

This vulnerability is present in Ghost from v2.2.0 to v6.54.0.

Patches

v6.54.1 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 meifukun for disclosing this vulnerability responsibly.

For more information

If you have any questions or comments about this advisory, email Ghost at security@ghost.org.

Affected versions

npm

PackageVulnerableFixed in
ghost
>= 2.2.0, < 6.54.1
6.54.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

ghost npm → 6.54.1

npm
npm install ghost@6.54.1
yarn
yarn add ghost@6.54.1
pnpm
pnpm add ghost@6.54.1

Severity breakdown

CVSS 3.1 6.7

CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L

Attack vector
Adjacent
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

Weakness

CWE-384: Session Fixation

Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

How to prevent it
  • Architecture and Design: Invalidate any existing session identifiers prior to authorizing a new user session.
  • Architecture and Design: For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.
  • Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-x3mg-q38v-m562
Ghost: Authorization Issue Allowed Author Role to Delete any Post
Medium Also affects ghost
GHSA-8575-cr6v-7jh4
Ghost: Stored XSS via SVG Uploads Bypassing Sanitization
High Also affects ghost
GHSA-r7f2-6fj8-6fg2
Ghost: Private IP Filtering Bypass via IPv6 Transition Addresses
Medium Also affects ghost
GHSA-322m-ff4g-9vx9
Ghost: Server-Side Request Forgery in Bookmark Fetching
Medium Also affects ghost
GHSA-fwh9-qg68-vxp4
Ghost: Regular Expression Denial of Service in Content Import
Medium Also affects ghost
GHSA-9m4w-fmjw-fvjq
Ghost: Regular Expression Denial of Service in External Media Inliner
Medium Also affects ghost
GHSA-hqq2-xqr2-fmx2
Ghost : Stored XSS via SVG Files in Content Imports
Medium Also affects ghost
GHSA-69qc-f5m6-889c
Ghost: Stored XSS via Embed Card Previews
High Also affects ghost
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor