Skip to main content
VulnerabilityPublished Updated

CVE-2026-29784: TryGhost Ghost · Cross-Site Request Forgery (CSRF)

Affects TryGhost GhostSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 6.19.3 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.19.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Ghost and ghost to 6.19.3.

Affected software

ProductAffectedFixed in
TryGhostGhostAffected
  • >=5.101.6 <6.19.3
Fixed in
  • 6.19.3
npmghostpkg:npm/ghostOther threatsAffected
  • >=5.101.6 <6.19.3
Fixed in
  • 6.19.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-29784, organizations should immediately upgrade all affected Ghost CMS instances to version 6.19.3 or later, where the vulnerability has been patched. Beyond patching, administrators should enforce strict Content Security Policies (CSP) to limit the execution of unauthorized scripts and reduce the risk of CSRF exploitation. Implementing multi-factor authentication (MFA) can add an additional layer of defense against session hijacking. Regularly auditing and monitoring user sessions and login activities can help detect anomalous behavior indicative of exploitation attempts. Web Application Firewalls (WAFs) configured to detect and block CSRF attack patterns can provide additional protection. Educating users about phishing risks and encouraging cautious interaction with unsolicited links or requests is also critical. Finally, developers should review and strengthen CSRF protections in custom integrations or plugins related to Ghost CMS.

Description

Ghost is a Node.js content management system. From version 5.101.6 to 6.19.2, incomplete CSRF protections around /session/verify made it possible to use OTCs in login sessions different from the requesting session. In some scenarios this might have made it easier for phishers to take over a Ghost site. This issue has been patched in version 6.19.3.

References

Community reviews

Loading reviews…