Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-29784 is a high-severity CSRF (CWE-352) vulnerability in Ghost Ghost. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-29784 is a cross-site request forgery (CSRF) vulnerability, classified under CWE-352, affecting Ghost, a Node.js content management system. The issue stems from incomplete CSRF protections around the /session/verify endpoint in versions 5.101.6 through 6.19.2. This flaw allows one-time codes (OTCs) intended for one login session to be used in a different session, with a CVSS v3.1 base score of 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H).
Remote unauthenticated attackers can exploit this vulnerability by tricking authenticated users into interacting with a malicious site or resource, such as through phishing. The high attack complexity and required user interaction enable phishers in certain scenarios to hijack login sessions and take over a Ghost site, potentially leading to high-impact confidentiality, integrity, and availability compromises.
The Ghost security advisory (GHSA-9m84-wc28-w895) and associated patch commit detail mitigation through updates to version 6.19.3, which addresses the incomplete CSRF protections in the /session/verify endpoint. Security practitioners should upgrade affected Ghost instances immediately and review configurations for proper CSRF token handling.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10163
Vulnerability Data
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…
more
for phishers to take over a Ghost site. This issue has been patched in version 6.19.3.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.
Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.