Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public Stripe Checkout endpoint (unauthenticated)
-
DeliveryInject HTML/JS via member name/content
-
ExploitAttach subscription to existing member
-
ExecutionGhost sends newsletter to member
-
PersistRecipient opens email
-
ImpactEmail client renders payload (XSS/HTML injection)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a Ghost instance (5.2.0 through <6.62.0) with Stripe-backed paid memberships enabled (the publicly reachable Stripe Checkout flow is the entry point) and the newsletter feature in use, since delivery of the injected content depends on a newsletter being sent to the targeted member. Exploitation is limited by: (1) victim interaction - a newsletter recipient must open the email (UI:P); and (2) the recipient's email client - script execution (XSS) only occurs in clients that render the injected markup, otherwise impact degrades to HTML injection/content spoofing. No attacker authentication is required (PR:N). |
| Impact | This is a genuine but conditional-impact issue rather than a drop-everything emergency. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N, 7.1) correctly captures the key traits: fully remote, low complexity, no privileges required (PR:N) - consistent with the description's 'without authentication' - but it DOES require passive victim interaction (UI:P), namely a newsletter recipient opening the email. No EPSS score, no CISA KEV listing, and no public exploit code are present in the supplied intelligence, so by the precision rules this is 'no public exploit identified at time of analysis.' The real-world severity is further tempered by a dependency chain the CVSS score cannot express: the XSS only fires 'depending on the recipient's email client' - most modern webmail clients (Gmail, Outlook.com) strip or sandbox script, so the practical outcome for many targets degrades to HTML injection / content spoofing rather than script execution. The most reliable impact is therefore integrity abuse (attaching paid subscriptions to arbitrary existing members, altering member names, injecting newsletter content), which matches the high integrity weighting (VI:H). Note a labeling conflict to verify: the CWE is CWE-863 (Incorrect Authorization) and the Tags include 'Authentication Bypass,' yet the mechanism is abuse/misauthorization of an unauthenticated Stripe Checkout flow plus output injection - not a true authentication bypass. Treat this as a medium-priority patch for Ghost instances that have Stripe-backed paid memberships and newsletters enabled. |
| Exploit ScenarioDerived | An unauthenticated attacker drives Ghost's public Stripe Checkout flow to attach a paid subscription to an existing member they do not own and overwrite that member's display name with an HTML/JavaScript payload. When Ghost later sends a newsletter that echoes the attacker-controlled member/content fields, a recipient opening the email in a permissive email client renders the injected markup, yielding HTML injection or XSS. No public proof-of-concept is identified in the supplied data; exploitation requires a victim to open the newsletter (UI:P). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Unauthenticated remote attackers can abuse the Stripe Checkout flow in Ghost CMS versions 5.2.0 through those prior to 6.62.0 to attach a paid subscription to an existing member account, change that member's stored name, and inject attacker-controlled markup into newsletters subsequently sent to that member. Depending on the recipient's email client, the injected content may render, degrading into HTML injection/content spoofing and, in clients that execute embedded script, cross-site scripting (XSS). Exploitation requires a Ghost instance with Stripe-backed paid memberships enabled and the newsletter feature in active use, plus a newsletter recipient opening the message (UI:P), so impact is conditional rather than immediate; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
RemediationAI
Upgrade Ghost to 6.62.0 or later, the first release outside the affected range and the vendor-released fix per the GitHub security advisory GHSA-qppx-rw6v-xjqf. If an upgrade cannot be applied immediately, the most effective compensating control is to disable Stripe-backed paid memberships so the vulnerable Checkout completion path is unreachable, at the cost of losing paid subscription revenue and checkout functionality until patched; alternatively, pause outbound newsletters, which removes the delivery vector for the injected content but leaves the subscription and member-name manipulation possible. Administrators who cannot disable either feature should treat the affected instance as untrusted-input-bearing, review member records for unexpected name changes or subscription attachments, and validate outbound newsletter content, understanding that these are detective controls rather than true mitigations. Apply the vendor advisory, and monitor the referenced VulnCheck advisory for any updated guidance; note that no public exploit code was identified at time of analysis, so prioritization should be driven by whether Stripe paid memberships and newsletters are enabled on a given instance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is an authorization flaw classed as CWE-863 (Incorrect Authorization) in Ghost's integration with Stripe Checkout for paid memberships. Ghost 5.2.0 introduced the affected checkout handling, and the flow does not adequately bind a completed Stripe Checkout session to the member identity that legitimately initiated it, letting an unauthenticated party complete a purchase that is applied to a pre-existing member record. That improper authorization permits three chained effects: subscription attachment to another member's account, modification of that member's name field, and storage of attacker-supplied content that is later emitted in newsletter email bodies. The stored-content path is what elevates the issue toward HTML injection/XSS, with the outcome determined by the recipient's mail client rendering behavior rather than by the server. The supplied CVSS v4.0 vector (7.1, AV:N/AC:L/AT:N/PR:N/UI:P, VI:H) aligns with the independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N): both confirm network reachability, no attacker authentication, and required victim interaction, with the highest-rated impact being to integrity rather than confidentiality or availability. CPE data identifies the affected package as cpe:2.3:a:tryghost:ghost.
Know when Ghost gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Unauthenticated remote abuse (PR:N) needing a recipient to open the newsletter (UI:R); payload executes in the email-client context (S:C) with HTML/XSS injection impacting confidentiality and integrity at low; vendor rates integrity higher (VI:H).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Ghost versions 5.2.0 through versions prior to 6.62.0 allow a remote attacker, without authentication, to abuse the Stripe Checkout flow to attach a paid subscription to an existing member, modify that member's name, and inject content into newsletters sent to the member. Depending on the recipient's email client, the injected content may be rendered, resulting in HTML injection or cross-site scripting (XSS).
Technical POC Analysis
Evidence scope warning: the supplied evidence is the GitHub advisory only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Ghost CMS, an open-source publishing and newsletter platform, contains a high-severity flaw for which no public exploit code has been identified that allows remote attackers to attach paid subscriptions to existing member accounts, alter stored member names, and inject attacker-controlled markup into newsletters sent to those members. Only organizations running Ghost with Stripe-backed paid memberships and an actively used newsletter feature are exposed, and abuse further depends on a recipient opening the affected message, but the injected content reaches subscribers directly under the organization's own brand and can degrade into content spoofing or script execution depending on the email client. Leadership should care because the newsletter is a trusted, high-reach channel: subscriber trust, data integrity, and brand reputation are the assets at risk, not just the platform itself.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Ghost CMS versions 5.105.0-5.130.5 and 6.0.0-6.10.3 contain an authentication bypass in their two-factor authentication
Arbitrary code execution in Ghost CMS versions 0.7.2 through 6.19.0 allows authenticated attackers with theme upload pri
An arbitrary file upload vulnerability in the file upload module of Ghost CMS v4.42.0 allows attackers to execute arbitr
An arbitrary file upload vulnerability in the file upload module of Ghost v4.39.0 allows attackers to execute arbitrary
SQL injection in Ghost CMS versions 3.24.0 through 6.19.0 allows unauthenticated attackers to read arbitrary database da
Ghost through 5.85.1 allows remote attackers to bypass an authentication rate-limit protection mechanism by using many X
Ghost through 5.76.0 allows stored XSS, and resultant privilege escalation in which a contributor can take over any acco
Ghost before 5.82.0 allows CSV Injection during a member CSV export. Rated high severity (CVSS 8.8), this vulnerability
Server-side request forgery (SSRF) vulnerability in Ghost CMS < 3.10.0 allows an attacker to scan local or external netw
Ghost before 5.42.1 allows remote attackers to read arbitrary files within the active theme's folder via /assets/built%2
Ghost is a Node.js CMS. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable, no authentication
Ghost is an open source content management system. Rated medium severity (CVSS 6.5), this vulnerability is remotely expl
EUVD-2026-90660
GHSA-gw54-gv3c-2g94
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB