Ghost
Monthly
Stored cross-site scripting in Ghost CMS 6.22.1 through 6.63.x lets an authenticated staff user with upload privileges host a browser-executable file on the site's own domain when the default local storage adapter is in use, potentially compromising other staff members' admin sessions. The flaw arises because the local storage adapter serves uploaded files with a Content-Type derived from the file extension instead of the inert type Ghost applies elsewhere, and it requires a victim staff or admin user to load the uploaded file's URL (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N, base 7.3). Sites using S3 or other cloud storage adapters are not affected, and the issue is fully neutralized in 6.64.0; there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
Authenticated Ghost Administrators on versions 6.10.3 through 6.63.x can achieve remote code execution by installing a crafted theme that abuses how Ghost resolves theme translation (i18n) files, allowing path traversal into attacker-controlled code. Exploitation requires a high-privilege Administrator account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) and no victim interaction beyond the attacker's own admin actions; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV). Because the attacker population is limited to trusted or already-compromised admin accounts rather than anonymous remote users, this is a high-severity but access-gated issue rather than a mass-exploitation priority.
Privilege escalation in Ghost CMS (versions 4.39.0 through 6.63.x) lets a staff user holding the 'view staff invites' permission read the secret tokens stored in pending invitations, including invitations issued for roles more privileged than their own, and then accept such an invite to elevate their account. Exploitation requires an authenticated staff session against the Admin API plus at least one pending higher-privilege invite at the time of attack, which is why the vendor rates attack complexity as high and the real-world priority is moderate rather than urgent. No public exploit has been identified at time of analysis, and the flaw is fixed in Ghost 6.64.0.
Stored cross-site scripting in Ghost CMS versions 5.94.0 through 6.63.x lets any staff user - including the lowest-privileged Contributor role - plant arbitrary HTML on the site's own domain through the bookmark-card feature. When a bookmark card was created, Ghost fetched the remote page's og:image and favicon URLs, trusted the URL file extension to decide the Content-Type of the stored file, and served the resulting file from the Ghost origin; an attacker-controlled source could therefore return HTML that Ghost saved and later served as an image, executing in the context of the site's domain. Because a victim staff member or administrator must subsequently open the post or editor containing the crafted card, this is an authenticated (CVSS PR:L), user-interaction-dependent stored XSS with scope change (S:C), rated 7.3; it is fixed in Ghost 6.64.0, and no public exploit code or active exploitation has been identified at time of analysis.
Stored cross-site scripting in Ghost CMS versions 2.1.0 through 6.63.x allows an attacker-controlled website to inject untrusted script into post content through the editor's oEmbed embed feature. A staff user with post-creation rights must first embed a URL pointing at the malicious site, at which point the site's self-declared oEmbed endpoint can return a 'photo', 'rich', or 'video' response containing an attacker-supplied html field; that payload is stored in the post's Lexical content and then executes in the Ghost admin editor, on the published site, and inside newsletter emails, potentially compromising an administrator's session. No public exploit identified at time of analysis, and the issue is fixed in version 6.64.0.
Stored cross-site scripting in Ghost CMS (4.22.0 through 6.64.x) allows any authenticated staff account - including the lowest-trust Contributor role - to upload unsanitized SVG media that is then served from the site's own domain, potentially compromising the admin sessions of other staff users who view it. Two upload paths are affected: SVG files supplied as video/media thumbnails, and files carrying a non-SVG extension (e.g. .png) alongside an image/svg+xml Content-Type, which the pre-patch allowlist validated only by extension. The vendor rates this 7.3, there is no CISA KEV entry and no public exploit code identified at time of analysis, and exploitation requires a higher-privileged user to actually view the malicious media (UI:R); the extension-spoofing path additionally depends on a storage adapter that serves files by content type (e.g. Amazon S3), so exposure varies by backend configuration.
Stored cross-site scripting in Ghost CMS 6.34.0 through 6.66.x allows an authenticated staff user, including a low-privilege Contributor, to store malicious scripts in post content through embed cards. The payload executes when another staff user opens the affected post in the Ghost admin editor, potentially compromising that user's admin session; it does not fire against anonymous front-end readers and requires victim interaction. The issue is fixed in Ghost 6.67.0, and no public exploit identified at time of analysis.
Remote code execution in Ghost CMS 6.56.0 through 6.66.x lets any authenticated staff user - including the lowest-privilege Contributor role - execute arbitrary commands on the Ghost server by creating a bookmark card that points to an attacker-controlled website serving a crafted SVG. The root cause is a code-injection flaw (CWE-94) in the SVG handling path of an image-processing library bundled with Ghost, and successful exploitation yields full confidentiality, integrity, and availability impact on the host. Exploitation requires a valid Ghost staff login (the vendor vector claims PR:N, but our assessed vector of PR:L/UI:N is the accurate prerequisite), and there is no public exploit identified at time of analysis. Ghost 6.67.0 is the fixed release.
Authenticated Ghost administrators can obtain remote code execution by uploading a crafted theme whose translation (i18n/locale) files abuse path traversal (CWE-22) to load attacker-controlled content that the Node.js server then executes. The vulnerability affects Ghost 6.10.3 through every release before 6.64.0, and exploitation requires a full administrator account with access to the theme upload/management feature - anonymous visitors, members, authors, and editors cannot trigger it, and no end-user interaction is needed once admin rights are held. No public exploit code has been identified at time of analysis, and this is an access-gated risk rather than a drive-by threat; the vendor has shipped a fixed release, with details in advisory GHSA-jj74-hc2q-xrvm and a parallel VulnCheck advisory.
Privilege escalation in Ghost 4.39.0 before 6.64.0 allows an authenticated staff user who has invite-viewing permission to read the secret token of a pending higher-privileged staff invite through the Admin API and then accept that invite to bind the elevated role to their own account. The issue is rated CVSS 4.0 base 7.7 High and is gated on a pending invite for a higher role being outstanding; no public exploit identified at time of analysis. Affected deployments should upgrade to Ghost 6.64.0 or later, as the vendor has released a patch.
Stored cross-site scripting (XSS) in Ghost CMS 2.5.0 through 6.63.x (before 6.64.0) lets an unauthenticated attacker inject malicious scripts into post content by hosting a crafted oEmbed photo response and persuading a content editor to embed its URL. The injected script executes in the Ghost editor, on published pages, and in newsletter emails, potentially compromising staff admin sessions. No public exploit code or active exploitation has been identified at time of analysis, and the vendor has released a patch in Ghost 6.64.0; the issue is considered credible but not an emergency because exploitation requires user interaction and targeted social engineering.
Stored cross-site scripting in Ghost CMS (5.94.0 up to but not including 6.64.0) lets any staff account - including low-privileged Contributors - plant persistent arbitrary HTML/JavaScript in the admin panel by creating a bookmark card whose icon or thumbnail URL points to an external resource that returns a non-image file, which Ghost then fetches, stores, and re-renders to other staff. Exploitation requires an authenticated low-privileged account (CVSS PR:L, confirmed by the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) plus a higher-privileged staff user (admin or editor) passively viewing the affected card in the admin interface (UI:P), so it is an insider/multi-author risk rather than an anonymous remote attack. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; the vendor has released a fix, making this a credible medium-to-high priority patching item for multi-author Ghost instances rather than a drop-everything emergency.
Stored cross-site scripting in Ghost CMS (6.22.1 through versions before 6.64.0) allows an authenticated staff user to upload a file that the default local storage adapter serves back from the site's own origin with an extension-derived content type, so a second staff member who views the upload in the admin context can have their session compromised. The attack is privilege-gated rather than a drive-by critical: it requires an existing staff account (PR:L), the default local storage adapter (instances using object-storage or CDN adapters on a separate origin are materially less exposed), and interaction by a victim staff user, typically one with higher privileges (UI:P). Vendor patch is available; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in Ghost CMS versions 0.5.3 through versions prior to 6.50.0 allows an authenticated user with limited privileges to inject unescaped content into the JSON-LD structured-data HTML tag produced by the {{ghost_head}} helper, which then executes as script in the session of a higher-privileged staff user who views the published page. The issue is tracked as CWE-79 and has a reported CVSS 4.0 base score of 8.6 (High); no public exploit was identified at time of analysis. Exploitation requires a valid low-privilege account and a staff victim visiting the affected page.
Authenticated Ghost members on sites running versions 5.9.0 through 6.44.0 can read comments they are not authorized to view, resulting in disclosure of restricted comment content through the native comments feature. The root cause is an input validation / query-logic authorization bypass (CWE-943), reachable over the network with low complexity and no user interaction; the vendor and VulnCheck assign a CVSS 4.0 base score of 7.1 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N), which our assessment maps to a CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, i.e. high confidentiality impact with no integrity or availability impact. Exposure is conditional on the site having membership and the native comments feature enabled and running an affected version; exploitation requires a valid low-privilege member account (PR:L), and no public exploit code has been identified at time of analysis.
Authenticated members on Ghost sites running versions 5.9.0 through 6.44.0 can delete comment likes and dislikes that belong to other users, allowing an authorization bypass that silently corrupts other members' comment engagement data. The flaw is an IDOR-style access-control failure (CWE-639) in the comment-like feature, reachable over the network with low complexity, but it requires a valid membership account and only permits integrity tampering with non-sensitive engagement counters - it does not expose data or affect availability. Vendor patch 6.44.1 is available, and no public exploit code was identified at time of analysis; the reported CVSS 4.0 score of 7.1 overstates real-world risk given the low-value target data and authenticated prerequisite.
Privilege escalation in Ghost CMS (versions 2.21.0 before 6.56.0) allows an authenticated low-privilege staff user to elevate their role to a higher-privilege staff position by exploiting missing authorization checks in the notifications system. Exploitation requires an existing staff account and passive interaction from a higher-privileged user (CVSS 4.0 PR:L/UI:P), so multi-author or multi-staff deployments are primarily at risk; single-author sites have negligible exposure. A vendor patch is available in Ghost 6.56.0, and no public exploit code has been identified at time of analysis.
Ghost 6.20.0 before 6.57.1 contains an improper session management flaw that allows an authenticated staff user who knows another staff member's password to log in as that staff user and bypass two-factor authentication. Successful exploitation can give the attacker the victim's administrative permissions, enabling unauthorized access to staff and admin functions. The issue requires valid staff credentials plus the target's password, so it is primarily an insider, credential-reuse, or post-phishing risk; no public exploit code was identified at time of analysis, and a vendor patch is available in 6.57.1.
Session invalidation bypass in Ghost 3.10.0 up to but not including 6.34.0 allows an attacker who already possesses a stolen session cookie to retain authenticated access after the legitimate user changes their password. The flaw is CWE-613 (insufficient session expiration); the assessed vector requires a pre-existing session (PR:L, AT:P, AC:H) and leads to high confidentiality and integrity impact once that prerequisite is met. No public exploit identified at time of analysis and no CISA KEV entry was provided, while the vendor has released a patch in Ghost 6.34.0 and later.
Staff account takeover in Ghost versions 5.8.0 through 6.34.0 allows an attacker with content-publishing privileges to craft malicious pages that, when viewed by an authenticated staff user in the admin interface, exploit improper input validation in the admin iframe to hijack the victim's account. The vulnerability requires a low-privileged authenticated attacker (PR:L) and user interaction (UI:R), making multi-author or open-contribution Ghost deployments the primary attack surface; single-author blogs without untrusted publishers are not exposed. No public exploit code was identified at time of analysis, and a vendor-released patch is available in version 6.34.0.
Untrusted script execution in the Ghost publishing platform's oEmbed preview feature affects versions from 2.5.0 through releases before 6.34.0, allowing an attacker to host malicious oEmbed content that runs scripts inside a staff user's authenticated admin session. Exploitation is unauthenticated from the attacker's side (CVSS 4.0 PR:N), but it requires a privileged user to actually preview or insert the crafted embed, so success depends on admin interaction and carries a changed scope because the payload executes in the victim's high-privilege browser context. No public exploit code has been identified at time of analysis and the flaw is not in CISA KEV, so the 8.6 base score should be read against this interaction-driven, no-observed-exploitation picture; a vendor patch is available in 6.34.0.
Unauthenticated staff enumeration in Ghost CMS affects every release from 2.10.0 up to (but not including) 6.63.0, allowing remote attackers to infer which staff accounts exist by comparing differences in the metadata returned by the public content API. The flaw is rated High (vendor CVSS 4.0 score 8.7; independent CVSS 3.1 assessment 8.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) because it requires no authentication, no user interaction, and only a network-reachable instance with its default content API exposed. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor has released a fix in Ghost 6.63.0.
Unauthenticated visitors can pull the full body of gated, members-only and paid-tier posts from Ghost 4.0.0 through 6.62.x by querying the platform's Content API directly, bypassing the membership restrictions that are supposed to withhold that content. The flaw is an authorization-checking failure (CWE-863) in post visibility filtering, scored 8.7 under CVSS 4.0 and assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - fully remote and unauthenticated, with high confidentiality impact and no integrity or availability effect. Impact is confined to sites that actually host gated content, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis; a vendor patch is available.
Suspended staff accounts in Ghost CMS can be reactivated through the self-service password reset flow, allowing a suspended user to restore their account and its original privileges in all versions before 6.62.0. The issue is an authenticated, post-login authorization gap rather than an anonymous takeover: the attacker must already hold valid credentials for a staff account that an administrator has suspended, which makes this primarily an insider, offboarding, or stolen-credential threat. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV), but the vendor-assigned CVSS 4.0 score of 8.7 and the independently assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) reflect high confidentiality, integrity, and availability impact wherever account suspension is the sole remaining control.
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).
Broken access control in Ghost Foundation Ghost 5.x enables any authenticated Author-role user to delete posts owned by other users, including content published by Editors and Administrators. The authorization failure originates in the post model's permissible() cascade, where the combined isAuthor-and-isDestroy condition is not handled, causing the guard to fall through and approve the deletion. No public exploit code has been identified at time of analysis, but the low attack complexity and minimal privilege requirement mean the flaw is trivially abusable by any Author-role account holder on the platform.
Web cache poisoning in the Ghost Node.js CMS before 6.37.0 lets an unauthenticated attacker inject an x-ghost-preview header that alters the rendered frontend response, which a shared caching layer then stores and serves to other visitors of the same page. When Ghost's public frontend and admin panel share a single domain, this request-specific preview output can be weaponized to hijack staff accounts; separate-domain deployments are not exposed. No public exploit is identified at time of analysis, and the issue carries a vendor CVSS of 9.6.
Cross-site scripting (JavaScript injection) in Ghost's ActivityPub client (@tryghost/activitypub) prior to version 3.1.0 allows a malicious federated server to embed attacker-controlled script in shared posts that executes in the browser of a victim Ghost user who views the content. The flaw stems from improper sanitization of post content received over ActivityPub federation, enabling session theft or actions performed in the victim's authenticated context. There is no public exploit identified at the time of analysis, and the issue is not listed in CISA KEV.
Cross-site request forgery (CSRF) in Ghost CMS versions 5.101.6 through 6.19.2 permits attackers to reuse one-time codes across different login sessions via the /session/verify endpoint, potentially enabling account takeover through phishing attacks. The vulnerability affects Ghost deployments on Node.js and related platforms, requiring no user authentication but relying on user interaction. A patch is available in Ghost version 6.19.3 and later.
Arbitrary code execution in Ghost CMS versions 0.7.2 through 6.19.0 allows authenticated attackers with theme upload privileges to execute malicious code on the server by crafting specially designed theme files. The vulnerability affects Ghost installations running on Node.js and requires high privileges to exploit, though successful attacks compromise complete server integrity with confidentiality, integrity, and availability impact. No patch is currently available for affected versions.
SQL injection in Ghost CMS versions 3.24.0 through 6.19.0 allows unauthenticated attackers to read arbitrary database data. Patch available.
Ghost is an open source content management system. [CVSS 8.8 HIGH]
Ghost CMS versions 5.121.0-5.130.5 and 6.0.0-6.10.3 incorrectly allow Staff Token authentication to access endpoints restricted to Staff Session authentication, enabling authenticated Admin/Owner-role users to perform unauthorized actions. An attacker with valid Staff Token credentials for elevated roles could bypass authentication restrictions and access sensitive endpoints not intended for token-based access. Patches are available in versions 5.130.6 and 6.11.0.
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 implementation that allows authenticated staff members to circumvent email-based 2FA requirements. An attacker with valid staff credentials can exploit this flaw to gain unauthorized access to administrative functions without completing the required second authentication factor. Patches are available in versions 5.130.6 and 6.11.0.
Ghost CMS versions 6.14.0 through before 6.27.0 allow an authenticated staff-level user to read files outside the configured local storage directory through a path traversal issue in the default LocalStorageBase storage adapter. The issue is authentication-gated and low severity, requires an existing staff account created by an administrator, and no public exploit identified at time of analysis; the vendor fixed it in Ghost 6.27.0.
Server-side request forgery in the Ghost CMS webhooks feature (versions 1.18.0 through releases prior to 6.27.0) allows an authenticated staff user who can create or edit webhooks to point a webhook target_url at internal hosts and force the Ghost server to issue requests to them. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N, score 2.7) confirms this is a network-reachable but privileged-account-required issue whose impact is limited to low confidentiality loss - blind or semi-blind probing rather than response retrieval or code execution - and there is no public exploit identified at time of analysis. Ghost 6.27.0 fixes the issue by routing webhook delivery through a request library that blocks internal IPs unless the operator explicitly opts in via a new configuration flag.
Authenticated Ghost members can read comments and comment replies they are not authorized to access on sites running Ghost 5.9.0 up to (but not including) 6.44.1. The defect is an authorization/input-validation flaw in the comments subsystem (CWE-943) that lets a low-privileged member account reach a code path intended for administrators, disclosing reply content across membership boundaries; the impact is read-only, with no write, post, or availability effect. Vendor-released patch: 6.44.1, and no public exploit identified at time of analysis.
Broken authorization in Ghost CMS versions 5.81.0 through 6.59.x lets an authenticated staff account with the Author role delete posts and pages authored by other users, including through bulk filter-based delete requests. The flaw is a missing primary-author check on the destroy path in the post model's permission logic (CWE-862), rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) - unauthenticated exploitation is not possible, and only multi-author instances with delegated Author accounts are realistically exposed. No public exploit code has been identified at time of analysis and there is no indication the issue has been actively exploited; Ghost fixed the behavior in version 6.60.0.
Authenticated staff holding the Editor or Super Editor role in Ghost CMS versions 0.5.0 through 6.63.x can escalate the privileges of Author and Contributor accounts by assigning their own Editor role to those users through the Ghost Admin API, even though they lack permission to grant that role. The flaw is bounded - attackers can only confer their own Editor-level role and cannot push targets to Administrator or Owner - and exploitation requires an existing, trusted staff account rather than outsider access. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but the vendor released a fix in version 6.64.0, so unpatched, multi-role Ghost publications should upgrade promptly.
Theme translation-file path traversal in Ghost CMS lets an authenticated Administrator read JSON files outside the active theme's directory, potentially exposing server configuration secrets such as database credentials or API keys stored in JSON. All Ghost releases from 1.20.0 up to but not including 6.64.0 are affected, with the fix shipped in 6.64.0; because exploitation requires the highest-privilege Administrator role (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, base 4.9) and yields confidentiality-only impact, this is a low-to-moderate priority issue rather than an anonymous remote attack. No public exploit code has been identified at time of analysis.
Any authenticated staff-level user on a self-hosted Ghost instance running versions 0.7.2 through 6.63.x could infer the relative ordering of other staff users' hashed password values through admin API query options, a low-severity side-channel disclosed as CWE-203 (Observable Discrepancy). The exposure is limited: raw hashes and passwords are never returned, and turning ordering metadata into a usable credential requires substantial additional effort, which is reflected in the CVSS:3.1 base score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) - a trusted staff account is a prerequisite, attack complexity is high, and only low confidentiality impact is assessed. There is no public exploit identified at time of analysis and no indication of active exploitation; the issue is fixed in Ghost 6.64.0 via the upstream PR and commit referenced in the advisory.
Server-side request forgery (SSRF) in Ghost CMS versions 6.0.9 through 6.64.x lets an unauthenticated remote attacker induce the server to issue limited HTTP requests to hosts on its internal network. The flaw is blind - no response body is ever returned to the attacker - so the practical value is confined to request-triggered side effects and liveness/timing inference rather than data exfiltration, and exploitation depends on the target deployment actually having reachable internal hosts (e.g. NAT64/DNS64 setups or flat internal networks). The vendor fixed the issue in Ghost 6.65.0; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, consistent with the assessed CVSS 3.1 score of 4.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N).
Blind server-side request forgery (SSRF) in Ghost CMS versions 6.54.1 through 6.64.x lets an unauthenticated remote attacker coerce the server into issuing limited HTTP requests to hosts on its internal network, using functionality such as the Webmentions feature to submit attacker-controlled URLs that are later fetched by Ghost's oembed/bookmark/favicon pipeline. The impact is constrained: no response body is returned to the attacker, so the attack yields only internal-host reachability probing rather than data exfiltration, and exploitation depends on winning a DNS-rebinding race (AC:H per the assessed vector, overall CVSS 4.0). No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the vendor-released patch is Ghost 6.65.0.
A denial-of-service condition in Ghost CMS affects versions 4.0.0 through 6.66.x, where a crafted content import file can drive catastrophic regular-expression backtracking and pin the Node.js event loop, leaving the server unresponsive. The vulnerability is only reachable by an authenticated Ghost Administrator (CVSS PR:H) who submits a malicious import through the built-in content import feature, so the practical risk is limited to environments where admin credentials are already compromised or misused. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing); vendor-released patch: 6.67.0.
Denial of service in Ghost CMS 5.37.0 through 6.66.x allows an authenticated administrator to pin server CPU and render the Ghost instance unresponsive by sending a crafted request to the external media inliner, which compiles attacker-influenced domain strings into unescaped regular expressions (CWE-1333, inefficient regular expression complexity / catastrophic backtracking). Exploitation requires a Ghost Administrator account (CVSS PR:H, AV:N/AC:L/UI:N/S:U/C:N/I:N/A:H, base score 4.9), so realistic risk is confined to malicious or compromised admin accounts rather than anonymous visitors or the read-only front end. No public exploit identified at time of analysis; the vendor fix is contained in Ghost 6.67.0.
Stored cross-site scripting in Ghost CMS versions 4.0.0 through 6.66.x allows an attacker to plant malicious JavaScript on the victim site's own domain by convincing an Administrator to import a crafted content archive containing an unsanitized SVG image. Per the CVSS vector (AV:N/AC:H/PR:N/UI:R), the attacker does not need credentials but the attack is not self-service: it depends on successful social engineering of a privileged Administrator to run the import (UI:R), and impact on staff users' admin sessions further depends on that stored SVG being rendered in an authenticated admin context. Exploitation is therefore conditional rather than opportunistic, and no public exploit code has been identified at time of analysis (no CISA KEV listing).
Path traversal in Ghost's theme translation loader (CWE-22) lets an authenticated administrator read JSON files outside the active theme directory by tampering with the locale/language setting, potentially exposing server configuration secrets. All Ghost releases from 1.20.0 up to but not including 6.64.0 are affected; the flaw requires a high-privilege admin account (CVSS 4.0 6.9 / assessed CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) and yields read-only disclosure of JSON-format files - no write, no code execution. There is no confirmed active exploitation (CISA KEV not listed) and no public exploit identified at time of analysis; a vendor patch is available in 6.64.0.
Ghost CMS versions from 0.7.2 up to (but not including) 6.64.0 leak password-hash ordering information to authenticated, staff-level users through the Admin API, allowing an insider or a holder of a compromised staff account to learn how other staff members' password hashes are sorted relative to one another. Exploitation requires authenticated staff access with Admin API reachability (PR:L), is rated high complexity (AC:H) because it depends on repeated, carefully crafted queries and the analysis of response discrepancies, and is bounded in impact: per the vendor advisory and independent assessment, the hashes themselves are not disclosed and practical password recovery is not enabled. No public exploit code and no confirmed active exploitation were identified at time of analysis, consistent with the very low CVSS 4.0 score of 2.3 and the assessed CVSS 3.1 vector of AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N.
Privilege escalation in Ghost CMS (TryGhost Ghost) versions 0.5.0 through before 6.64.0 allows an authenticated Editor or Super Editor to assign their own elevated role to other staff accounts, promoting existing Author and Contributor users to Editor or Super Editor without holding the authority to do so. Exploitation is gated by the attacker already holding an Editor or Super Editor account (PR:L in the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, vendor CVSS 4.0 score 5.3), so anonymous outsiders cannot abuse it, and the effect is limited to integrity rather than confidentiality or availability. A vendor-supplied patch is available and no public exploit code has been identified at time of analysis.
Server-side request forgery in Ghost 3.20.2 through 6.50.x allows authenticated staff users to trigger outbound HTTP requests to arbitrary URLs via the image dimension refetching feature. Attackers can point image cards at internal network endpoints or cloud metadata services (e.g., 169.254.169.254) to access resources unavailable from the public internet. No public exploit code identified at time of analysis; the vendor has released a patch in Ghost 6.51.0.
Path traversal in the Ghost CMS ImageSize service (versions 6.14.0 through releases prior to 6.27.0) lets an authenticated staff user with elevated privileges read arbitrary local files from the server outside the intended data/storage directories. Exploitation is network-reachable and requires no user interaction, but is gated behind valid staff credentials, so the impact is bounded to file disclosure (confidentiality only, with no integrity or availability effect). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV), making this a moderate, authentication-gated risk (CVSS 5.1) that the vendor has fixed in Ghost 6.27.0.
Server-side request forgery in Ghost (TryGhost) versions 1.18.0 through 6.27.0 allows an authenticated staff-level user with permission to create or edit webhooks to make the Ghost server send requests to internal network resources, including cloud metadata services. Vendor scoring is CVSS 5.1 with PR:H, reflecting that the attacker must already hold privileged access; no public exploit code was identified at time of analysis and there is no CISA KEV listing.
Cross-site request forgery in the post feedback function of Ghost CMS lets an attacker submit feedback on behalf of any logged-in member who visits a crafted link, affecting versions 5.19.0 up to (but not including) 6.57.1. The attacker needs no account on the target site, but the attack only works against a victim who is an authenticated member with an active session and who follows the malicious page, and the resulting impact is integrity-only - unwanted feedback entries with no confidentiality or availability effect (CVSS 3.1: 5.3). No public exploit code was identified at time of analysis, and the vendor has released a fix in Ghost 6.57.1.
Information disclosure in Ghost CMS affects versions 5.125.1 up to but not including 6.57.1, where the Admin Feedback endpoint omits a proper authorization check and lets an authenticated staff user retrieve member records they should not be able to see. The flaw is credential-gated (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), needs no user interaction, and is limited to confidentiality of member data with no integrity or availability impact, which is why the published 5.3 base score reflects a moderate rather than emergency-level risk. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, so realistic exposure depends mainly on how many staff accounts an instance provisions and how sensitive its member records are.
A race condition in Ghost CMS's staff invitation acceptance flow (affecting versions 0.5.0 through 6.22.x) allows someone holding a valid invitation token to create more than one user account from that single-use invite by firing concurrent acceptance requests before the token is marked consumed. The impact is integrity-only and low (independent assessment: CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, matching the published 5.3), since exploitation is opportunistic rather than deterministic and requires a legitimately issued staff invite token; no public exploit code or confirmed active exploitation was identified at time of analysis. Ghost 6.23.0 contains the vendor fix.
Authenticated low-privilege staff users on Ghost sites can read Admin API keys that should only be visible to higher-privileged accounts, handing them credentials intended for trusted integrations. The exposure affects the Ghost npm package from 3.23.0 through 6.22.x and is resolved in 6.23.0, with the CVSS vector (PR:L, AV:N, no UI) confirming that a valid staff login on a remote instance is the only prerequisite. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the independent assessment rates this as a genuine but modest-severity information-disclosure and privilege-escalation risk driven by insider or compromised-staff scenarios rather than unauthenticated remote attack.
The setup endpoint in Ghost CMS returns the site owner's email address to any remote, unauthenticated visitor, exposing every release from 0.8.0 up to but not including 6.23.0. Exploitation requires no account, no user interaction, and no non-default configuration, but the yield is limited to a single email address - no credentials, content, or system access - so realistic impact is reconnaissance and phishing enablement rather than direct compromise. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and vendor patching is available in 6.23.0.
Unauthenticated attackers can read theme template and metadata files from internet-facing Ghost blogs running any version before 6.20.0 by supplying URL-encoded file paths that slip past the platform's file-extension validation, exposing theme source and configuration but not member data, user records, or site secrets. The flaw requires no special configuration and works against a default installation (CVSS 4.0 base 6.9; independent assessment scores it CVSS 3.1 AV:N/AC:L/PR:N/UI:N with only low confidentiality impact, no integrity or availability impact). No public exploit code has been identified at time of analysis, and the vendor-released fix is Ghost 6.20.0.
Authenticated staff-level users of Ghost CMS (versions 5.42.2 up to but not including 6.58.0) can infer other staff users' password hashes by supplying Admin API bulk post and page edit/delete filters that reference restricted fields such as authors.password. Because the bulk operation code paths fail to reject these restricted-field filters, the match/no-match behaviour acts as a boolean oracle that leaks information about the stored hash, which an attacker can then attack with offline password-guessing (cracking) - it does not hand over credentials directly. This is a genuine but modest-priority authenticated information disclosure (CVSS 5.3, assessed CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, CWE-203); there is no CISA KEV entry and no public exploit identified at time of analysis, and the issue is fully remediated in Ghost 6.58.0.
Unauthenticated visitors to Ghost instances running versions 5.3.0 through 6.57.x in private mode with comments enabled can read comments that private mode should restrict, bypassing the site's privacy settings. This is a low-impact confidentiality flaw limited to comment text disclosure-no write access, account takeover, or integrity impact-and it requires the configuration of private mode plus comments being enabled. Vendor-released patch: 6.58.0; no public exploit identified at time of analysis.
Authenticated low-privilege staff users on Ghost CMS versions 4.3.0 through 6.57.x can abuse staff tokens to modify posts beyond the permissions granted to their role, effectively bypassing the post-editing restrictions that separate Authors and Contributors from higher-privileged editors. Exploitation requires a valid, already-provisioned staff account (PR:L in both the reported and independently assessed vectors), so it is not reachable by anonymous internet users, and the impact is confined to unauthorized content modification (integrity) with no data disclosure or availability loss. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is a moderate, authenticated-only authorization flaw rather than a widespread-exploitation priority; a vendor patch is available from Ghost in version 6.58.0.
Authenticated Ghost site members on versions 5.3.0 through 6.61.x can retrieve the post excerpts (preview snippets) of gated, members-only or premium posts they are not entitled to read, because the excerpts endpoint fails to enforce the same access checks applied to full post content. The exposure is limited to excerpt text rather than complete article bodies, so the practical impact is partial content disclosure, and sites that publish no gated or paywalled content are unaffected. Any registered member account - including a free-tier member with no subscription - is sufficient to trigger the issue; no public exploit code has been identified at time of analysis, and no confirmed active exploitation (CISA KEV) has been reported.
Staff invite acceptance in Ghost before 6.62.0 allows the holder of a valid invite token to create their account with an arbitrary, attacker-chosen email address instead of the address the invite was issued to, breaking the binding between an invited identity and the resulting staff account. Exploitation is authenticated (CVSS PR:L) and depends on a legitimate invite token already existing and having been leaked, forwarded, or otherwise exposed - a remote unauthenticated attacker cannot mint an invite and trigger this on their own - and the assessed impact is integrity-only with no confidentiality or availability loss (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), making this a low-to-moderate risk issue despite the 'authentication bypass' label. No public exploit identified at time of analysis; the vendor has released a fix in Ghost 6.62.0.
Blind password hash disclosure in Ghost Admin API versions prior to 6.54.1 allows any authenticated staff-level user to retrieve hashed passwords of other staff accounts by crafting filtered API queries against the posts or pages browse endpoints. The root cause is insufficient field-level access control in MongoDB filter queries, exposing internal authentication fields (CWE-200). No active exploitation is confirmed (not in CISA KEV), and downstream account takeover is partially mitigated by Ghost's Device Verification and email MFA features, though the hash disclosure itself is confirmed and unambiguously fixed in 6.54.1.
Cross-site scripting in Ghost CMS (versions 5.26.0 through 6.54.0) allows a high-privileged administrator to plant arbitrary JavaScript via the Universal Import feature, which fails to sanitize the `feature_image_caption` field and link card URLs before storing and rendering them. The fix in v6.54.1 introduces DOMPurify sanitization across both the Ember-based admin post history modal and the Node.js frontend rendering pipeline, alongside a strict URL protocol allowlist in the JSON-to-HTML importer. No active exploitation is confirmed (not in CISA KEV) and no public proof-of-concept is known; the high-privilege prerequisite substantially limits the realistic attacker pool.
Server-side request forgery (SSRF) filter bypass in Ghost CMS 6.0.9 through 6.21.0 allows remote unauthenticated attackers to direct the application to reach internal network services by supplying IPv6 literals that map to private IPv4 addresses, circumventing Ghost's outbound IP blocklist. The root cause is CWE-184 (Incomplete List of Disallowed Inputs): the filter validates against RFC 1918 private ranges but does not normalize IPv6-mapped IPv4 notation before comparison. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists; Ghost 6.21.1 resolves the issue.
DNS rebinding bypasses Ghost CMS's private-IP validation for outbound HTTP requests, enabling server-side request forgery (SSRF) against internal network resources. Versions 6.0.9 through 6.21.0 are affected; the root cause is a TOCTOU race (CWE-367) between Ghost's allowlist check and the actual TCP connection, which a DNS-rebinding attacker exploits by switching DNS records between check-time and connect-time. No public exploit code identified and not listed in CISA KEV, but the scope-changed CVSS rating (S:C) reflects that successful exploitation escapes Ghost's network boundary into adjacent internal infrastructure.
Server-side request forgery in Ghost CMS versions 6.19.4 through 6.21.1 allows authenticated staff users to pivot the Ghost server into making arbitrary outbound HTTP requests, including to internal network hosts and cloud instance metadata endpoints. The vulnerable code path is Ghost's post re-rendering pipeline, which fetches image dimensions from URLs stored in image cards without validating those URLs against a trusted host allowlist. No public exploit has been identified at time of analysis, and a vendor-released patch is available in 6.21.1.
Ghost CMS versions 5.18.0 through 6.21.1 expose registered member email addresses to unauthenticated enumeration via observable discrepancies in the members signin endpoint responses. Any Ghost site with the members feature active is affected, allowing an attacker to silently probe whether arbitrary email addresses belong to site subscribers. No public exploit or active exploitation (CISA KEV) has been identified; vendor patch is available in 6.21.1.
Stored cross-site scripting in Ghost CMS (versions 6.19.4 through 6.21.0) is enabled by the Admin API file upload endpoint accepting and preserving attacker-supplied Content-Type headers without server-side validation. When Ghost is configured with S3 or GCS storage backends that serve uploaded files from the same origin as the site, an authenticated attacker can upload a file with a crafted Content-Type (e.g., text/html) that causes browsers to execute it as HTML or JavaScript, enabling stored XSS against visitors and staff. No public exploit code has been identified at time of analysis, and the vulnerability is fixed in Ghost 6.21.1.
Filter validation bypass in Ghost CMS public API endpoints exposes private fields - including password hashes - to unauthenticated remote attackers via repeated brute-force probing. Instances running SQLite are most severely impacted: full password hashes are recoverable, enabling offline cracking. MySQL-backed instances leak structurally degraded hashes (case information lost), which the vendor assesses would render subsequent cracking attempts fruitless. No public exploit code exists and the vulnerability is not in CISA KEV at time of analysis, but the unauthenticated, network-accessible nature of the flaw lowers the bar for opportunistic discovery.
Ghost is a Node.js content management system. In versions 5.38.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost’s media inliner mechanism allows staff users in possession of a valid authentication token for the Ghost Admin API to exfiltrate data from internal systems via SSRF. [CVSS 2.7 LOW]
SQL injection in Ghost's Admin API members/events endpoint enables authenticated administrators to execute arbitrary database queries, affecting versions 5.90.0-5.130.5 and 6.0.0-6.10.3. An attacker with valid Admin API credentials could exploit this to extract, modify, or delete sensitive data stored in the Ghost database. Patches are available in versions 5.130.6 and 6.11.0.
Server-Side Request Forgery (SSRF) vulnerability in Ghost allows an attacker to access internal resources.0.0 through 6.0.8, from 5.99.0 through 5.130.3. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Ghost is a Node.js content management system. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Ghost through 5.85.1 allows remote attackers to bypass an authentication rate-limit protection mechanism by using many X-Forwarded-For headers with different values. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Ghost before 5.82.0 allows CSV Injection during a member CSV export. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Ghost through 5.76.0 allows stored XSS, and resultant privilege escalation in which a contributor can take over any account, via an SVG profile picture that contains JavaScript code to interact with. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Ghost before 5.76.0 allows XSS via a post excerpt in excerpt.js. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Cross-Site Scripting (XSS) vulnerability could allow attackers to inject malicious scripts into web pages viewed by other users.
Ghost is an open source content management system. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Ghost is an app for new-media creators with tools to build a website, publish content, send newsletters, and offer paid subscriptions to members. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Exposure of Sensitive Information vulnerability could allow attackers to access sensitive data that should not be disclosed.
Ghost before 5.42.1 allows remote attackers to read arbitrary files within the active theme's folder via /assets/built%2F..%2F..%2F/ directory traversal. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Ghost 5.35.0 allows authorization bypass: contributors can view draft posts of other users, which is arguably inconsistent with a security policy in which a contributor's draft can only be read by. Rated medium severity (CVSS 5.7), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A user enumeration vulnerability exists in the login functionality of Ghost Foundation Ghost 5.9.4. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An authentication bypass vulnerability exists in the newsletter subscription functionality of Ghost Foundation Ghost 5.9.4. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
An arbitrary file upload vulnerability in the file upload module of Ghost CMS v4.42.0 allows attackers to execute arbitrary code via a crafted file. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An arbitrary file upload vulnerability in the file upload module of Ghost v4.39.0 allows attackers to execute arbitrary code via a crafted SVG file. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Ghost is a Node.js content management system. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Ghost is a Node.js CMS. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable, no authentication required. Public exploit code available and no vendor patch available.
Stored cross-site scripting in Ghost CMS 6.22.1 through 6.63.x lets an authenticated staff user with upload privileges host a browser-executable file on the site's own domain when the default local storage adapter is in use, potentially compromising other staff members' admin sessions. The flaw arises because the local storage adapter serves uploaded files with a Content-Type derived from the file extension instead of the inert type Ghost applies elsewhere, and it requires a victim staff or admin user to load the uploaded file's URL (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N, base 7.3). Sites using S3 or other cloud storage adapters are not affected, and the issue is fully neutralized in 6.64.0; there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
Authenticated Ghost Administrators on versions 6.10.3 through 6.63.x can achieve remote code execution by installing a crafted theme that abuses how Ghost resolves theme translation (i18n) files, allowing path traversal into attacker-controlled code. Exploitation requires a high-privilege Administrator account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) and no victim interaction beyond the attacker's own admin actions; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV). Because the attacker population is limited to trusted or already-compromised admin accounts rather than anonymous remote users, this is a high-severity but access-gated issue rather than a mass-exploitation priority.
Privilege escalation in Ghost CMS (versions 4.39.0 through 6.63.x) lets a staff user holding the 'view staff invites' permission read the secret tokens stored in pending invitations, including invitations issued for roles more privileged than their own, and then accept such an invite to elevate their account. Exploitation requires an authenticated staff session against the Admin API plus at least one pending higher-privilege invite at the time of attack, which is why the vendor rates attack complexity as high and the real-world priority is moderate rather than urgent. No public exploit has been identified at time of analysis, and the flaw is fixed in Ghost 6.64.0.
Stored cross-site scripting in Ghost CMS versions 5.94.0 through 6.63.x lets any staff user - including the lowest-privileged Contributor role - plant arbitrary HTML on the site's own domain through the bookmark-card feature. When a bookmark card was created, Ghost fetched the remote page's og:image and favicon URLs, trusted the URL file extension to decide the Content-Type of the stored file, and served the resulting file from the Ghost origin; an attacker-controlled source could therefore return HTML that Ghost saved and later served as an image, executing in the context of the site's domain. Because a victim staff member or administrator must subsequently open the post or editor containing the crafted card, this is an authenticated (CVSS PR:L), user-interaction-dependent stored XSS with scope change (S:C), rated 7.3; it is fixed in Ghost 6.64.0, and no public exploit code or active exploitation has been identified at time of analysis.
Stored cross-site scripting in Ghost CMS versions 2.1.0 through 6.63.x allows an attacker-controlled website to inject untrusted script into post content through the editor's oEmbed embed feature. A staff user with post-creation rights must first embed a URL pointing at the malicious site, at which point the site's self-declared oEmbed endpoint can return a 'photo', 'rich', or 'video' response containing an attacker-supplied html field; that payload is stored in the post's Lexical content and then executes in the Ghost admin editor, on the published site, and inside newsletter emails, potentially compromising an administrator's session. No public exploit identified at time of analysis, and the issue is fixed in version 6.64.0.
Stored cross-site scripting in Ghost CMS (4.22.0 through 6.64.x) allows any authenticated staff account - including the lowest-trust Contributor role - to upload unsanitized SVG media that is then served from the site's own domain, potentially compromising the admin sessions of other staff users who view it. Two upload paths are affected: SVG files supplied as video/media thumbnails, and files carrying a non-SVG extension (e.g. .png) alongside an image/svg+xml Content-Type, which the pre-patch allowlist validated only by extension. The vendor rates this 7.3, there is no CISA KEV entry and no public exploit code identified at time of analysis, and exploitation requires a higher-privileged user to actually view the malicious media (UI:R); the extension-spoofing path additionally depends on a storage adapter that serves files by content type (e.g. Amazon S3), so exposure varies by backend configuration.
Stored cross-site scripting in Ghost CMS 6.34.0 through 6.66.x allows an authenticated staff user, including a low-privilege Contributor, to store malicious scripts in post content through embed cards. The payload executes when another staff user opens the affected post in the Ghost admin editor, potentially compromising that user's admin session; it does not fire against anonymous front-end readers and requires victim interaction. The issue is fixed in Ghost 6.67.0, and no public exploit identified at time of analysis.
Remote code execution in Ghost CMS 6.56.0 through 6.66.x lets any authenticated staff user - including the lowest-privilege Contributor role - execute arbitrary commands on the Ghost server by creating a bookmark card that points to an attacker-controlled website serving a crafted SVG. The root cause is a code-injection flaw (CWE-94) in the SVG handling path of an image-processing library bundled with Ghost, and successful exploitation yields full confidentiality, integrity, and availability impact on the host. Exploitation requires a valid Ghost staff login (the vendor vector claims PR:N, but our assessed vector of PR:L/UI:N is the accurate prerequisite), and there is no public exploit identified at time of analysis. Ghost 6.67.0 is the fixed release.
Authenticated Ghost administrators can obtain remote code execution by uploading a crafted theme whose translation (i18n/locale) files abuse path traversal (CWE-22) to load attacker-controlled content that the Node.js server then executes. The vulnerability affects Ghost 6.10.3 through every release before 6.64.0, and exploitation requires a full administrator account with access to the theme upload/management feature - anonymous visitors, members, authors, and editors cannot trigger it, and no end-user interaction is needed once admin rights are held. No public exploit code has been identified at time of analysis, and this is an access-gated risk rather than a drive-by threat; the vendor has shipped a fixed release, with details in advisory GHSA-jj74-hc2q-xrvm and a parallel VulnCheck advisory.
Privilege escalation in Ghost 4.39.0 before 6.64.0 allows an authenticated staff user who has invite-viewing permission to read the secret token of a pending higher-privileged staff invite through the Admin API and then accept that invite to bind the elevated role to their own account. The issue is rated CVSS 4.0 base 7.7 High and is gated on a pending invite for a higher role being outstanding; no public exploit identified at time of analysis. Affected deployments should upgrade to Ghost 6.64.0 or later, as the vendor has released a patch.
Stored cross-site scripting (XSS) in Ghost CMS 2.5.0 through 6.63.x (before 6.64.0) lets an unauthenticated attacker inject malicious scripts into post content by hosting a crafted oEmbed photo response and persuading a content editor to embed its URL. The injected script executes in the Ghost editor, on published pages, and in newsletter emails, potentially compromising staff admin sessions. No public exploit code or active exploitation has been identified at time of analysis, and the vendor has released a patch in Ghost 6.64.0; the issue is considered credible but not an emergency because exploitation requires user interaction and targeted social engineering.
Stored cross-site scripting in Ghost CMS (5.94.0 up to but not including 6.64.0) lets any staff account - including low-privileged Contributors - plant persistent arbitrary HTML/JavaScript in the admin panel by creating a bookmark card whose icon or thumbnail URL points to an external resource that returns a non-image file, which Ghost then fetches, stores, and re-renders to other staff. Exploitation requires an authenticated low-privileged account (CVSS PR:L, confirmed by the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) plus a higher-privileged staff user (admin or editor) passively viewing the affected card in the admin interface (UI:P), so it is an insider/multi-author risk rather than an anonymous remote attack. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; the vendor has released a fix, making this a credible medium-to-high priority patching item for multi-author Ghost instances rather than a drop-everything emergency.
Stored cross-site scripting in Ghost CMS (6.22.1 through versions before 6.64.0) allows an authenticated staff user to upload a file that the default local storage adapter serves back from the site's own origin with an extension-derived content type, so a second staff member who views the upload in the admin context can have their session compromised. The attack is privilege-gated rather than a drive-by critical: it requires an existing staff account (PR:L), the default local storage adapter (instances using object-storage or CDN adapters on a separate origin are materially less exposed), and interaction by a victim staff user, typically one with higher privileges (UI:P). Vendor patch is available; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in Ghost CMS versions 0.5.3 through versions prior to 6.50.0 allows an authenticated user with limited privileges to inject unescaped content into the JSON-LD structured-data HTML tag produced by the {{ghost_head}} helper, which then executes as script in the session of a higher-privileged staff user who views the published page. The issue is tracked as CWE-79 and has a reported CVSS 4.0 base score of 8.6 (High); no public exploit was identified at time of analysis. Exploitation requires a valid low-privilege account and a staff victim visiting the affected page.
Authenticated Ghost members on sites running versions 5.9.0 through 6.44.0 can read comments they are not authorized to view, resulting in disclosure of restricted comment content through the native comments feature. The root cause is an input validation / query-logic authorization bypass (CWE-943), reachable over the network with low complexity and no user interaction; the vendor and VulnCheck assign a CVSS 4.0 base score of 7.1 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N), which our assessment maps to a CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, i.e. high confidentiality impact with no integrity or availability impact. Exposure is conditional on the site having membership and the native comments feature enabled and running an affected version; exploitation requires a valid low-privilege member account (PR:L), and no public exploit code has been identified at time of analysis.
Authenticated members on Ghost sites running versions 5.9.0 through 6.44.0 can delete comment likes and dislikes that belong to other users, allowing an authorization bypass that silently corrupts other members' comment engagement data. The flaw is an IDOR-style access-control failure (CWE-639) in the comment-like feature, reachable over the network with low complexity, but it requires a valid membership account and only permits integrity tampering with non-sensitive engagement counters - it does not expose data or affect availability. Vendor patch 6.44.1 is available, and no public exploit code was identified at time of analysis; the reported CVSS 4.0 score of 7.1 overstates real-world risk given the low-value target data and authenticated prerequisite.
Privilege escalation in Ghost CMS (versions 2.21.0 before 6.56.0) allows an authenticated low-privilege staff user to elevate their role to a higher-privilege staff position by exploiting missing authorization checks in the notifications system. Exploitation requires an existing staff account and passive interaction from a higher-privileged user (CVSS 4.0 PR:L/UI:P), so multi-author or multi-staff deployments are primarily at risk; single-author sites have negligible exposure. A vendor patch is available in Ghost 6.56.0, and no public exploit code has been identified at time of analysis.
Ghost 6.20.0 before 6.57.1 contains an improper session management flaw that allows an authenticated staff user who knows another staff member's password to log in as that staff user and bypass two-factor authentication. Successful exploitation can give the attacker the victim's administrative permissions, enabling unauthorized access to staff and admin functions. The issue requires valid staff credentials plus the target's password, so it is primarily an insider, credential-reuse, or post-phishing risk; no public exploit code was identified at time of analysis, and a vendor patch is available in 6.57.1.
Session invalidation bypass in Ghost 3.10.0 up to but not including 6.34.0 allows an attacker who already possesses a stolen session cookie to retain authenticated access after the legitimate user changes their password. The flaw is CWE-613 (insufficient session expiration); the assessed vector requires a pre-existing session (PR:L, AT:P, AC:H) and leads to high confidentiality and integrity impact once that prerequisite is met. No public exploit identified at time of analysis and no CISA KEV entry was provided, while the vendor has released a patch in Ghost 6.34.0 and later.
Staff account takeover in Ghost versions 5.8.0 through 6.34.0 allows an attacker with content-publishing privileges to craft malicious pages that, when viewed by an authenticated staff user in the admin interface, exploit improper input validation in the admin iframe to hijack the victim's account. The vulnerability requires a low-privileged authenticated attacker (PR:L) and user interaction (UI:R), making multi-author or open-contribution Ghost deployments the primary attack surface; single-author blogs without untrusted publishers are not exposed. No public exploit code was identified at time of analysis, and a vendor-released patch is available in version 6.34.0.
Untrusted script execution in the Ghost publishing platform's oEmbed preview feature affects versions from 2.5.0 through releases before 6.34.0, allowing an attacker to host malicious oEmbed content that runs scripts inside a staff user's authenticated admin session. Exploitation is unauthenticated from the attacker's side (CVSS 4.0 PR:N), but it requires a privileged user to actually preview or insert the crafted embed, so success depends on admin interaction and carries a changed scope because the payload executes in the victim's high-privilege browser context. No public exploit code has been identified at time of analysis and the flaw is not in CISA KEV, so the 8.6 base score should be read against this interaction-driven, no-observed-exploitation picture; a vendor patch is available in 6.34.0.
Unauthenticated staff enumeration in Ghost CMS affects every release from 2.10.0 up to (but not including) 6.63.0, allowing remote attackers to infer which staff accounts exist by comparing differences in the metadata returned by the public content API. The flaw is rated High (vendor CVSS 4.0 score 8.7; independent CVSS 3.1 assessment 8.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) because it requires no authentication, no user interaction, and only a network-reachable instance with its default content API exposed. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor has released a fix in Ghost 6.63.0.
Unauthenticated visitors can pull the full body of gated, members-only and paid-tier posts from Ghost 4.0.0 through 6.62.x by querying the platform's Content API directly, bypassing the membership restrictions that are supposed to withhold that content. The flaw is an authorization-checking failure (CWE-863) in post visibility filtering, scored 8.7 under CVSS 4.0 and assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - fully remote and unauthenticated, with high confidentiality impact and no integrity or availability effect. Impact is confined to sites that actually host gated content, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis; a vendor patch is available.
Suspended staff accounts in Ghost CMS can be reactivated through the self-service password reset flow, allowing a suspended user to restore their account and its original privileges in all versions before 6.62.0. The issue is an authenticated, post-login authorization gap rather than an anonymous takeover: the attacker must already hold valid credentials for a staff account that an administrator has suspended, which makes this primarily an insider, offboarding, or stolen-credential threat. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV), but the vendor-assigned CVSS 4.0 score of 8.7 and the independently assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) reflect high confidentiality, integrity, and availability impact wherever account suspension is the sole remaining control.
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).
Broken access control in Ghost Foundation Ghost 5.x enables any authenticated Author-role user to delete posts owned by other users, including content published by Editors and Administrators. The authorization failure originates in the post model's permissible() cascade, where the combined isAuthor-and-isDestroy condition is not handled, causing the guard to fall through and approve the deletion. No public exploit code has been identified at time of analysis, but the low attack complexity and minimal privilege requirement mean the flaw is trivially abusable by any Author-role account holder on the platform.
Web cache poisoning in the Ghost Node.js CMS before 6.37.0 lets an unauthenticated attacker inject an x-ghost-preview header that alters the rendered frontend response, which a shared caching layer then stores and serves to other visitors of the same page. When Ghost's public frontend and admin panel share a single domain, this request-specific preview output can be weaponized to hijack staff accounts; separate-domain deployments are not exposed. No public exploit is identified at time of analysis, and the issue carries a vendor CVSS of 9.6.
Cross-site scripting (JavaScript injection) in Ghost's ActivityPub client (@tryghost/activitypub) prior to version 3.1.0 allows a malicious federated server to embed attacker-controlled script in shared posts that executes in the browser of a victim Ghost user who views the content. The flaw stems from improper sanitization of post content received over ActivityPub federation, enabling session theft or actions performed in the victim's authenticated context. There is no public exploit identified at the time of analysis, and the issue is not listed in CISA KEV.
Cross-site request forgery (CSRF) in Ghost CMS versions 5.101.6 through 6.19.2 permits attackers to reuse one-time codes across different login sessions via the /session/verify endpoint, potentially enabling account takeover through phishing attacks. The vulnerability affects Ghost deployments on Node.js and related platforms, requiring no user authentication but relying on user interaction. A patch is available in Ghost version 6.19.3 and later.
Arbitrary code execution in Ghost CMS versions 0.7.2 through 6.19.0 allows authenticated attackers with theme upload privileges to execute malicious code on the server by crafting specially designed theme files. The vulnerability affects Ghost installations running on Node.js and requires high privileges to exploit, though successful attacks compromise complete server integrity with confidentiality, integrity, and availability impact. No patch is currently available for affected versions.
SQL injection in Ghost CMS versions 3.24.0 through 6.19.0 allows unauthenticated attackers to read arbitrary database data. Patch available.
Ghost is an open source content management system. [CVSS 8.8 HIGH]
Ghost CMS versions 5.121.0-5.130.5 and 6.0.0-6.10.3 incorrectly allow Staff Token authentication to access endpoints restricted to Staff Session authentication, enabling authenticated Admin/Owner-role users to perform unauthorized actions. An attacker with valid Staff Token credentials for elevated roles could bypass authentication restrictions and access sensitive endpoints not intended for token-based access. Patches are available in versions 5.130.6 and 6.11.0.
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 implementation that allows authenticated staff members to circumvent email-based 2FA requirements. An attacker with valid staff credentials can exploit this flaw to gain unauthorized access to administrative functions without completing the required second authentication factor. Patches are available in versions 5.130.6 and 6.11.0.
Ghost CMS versions 6.14.0 through before 6.27.0 allow an authenticated staff-level user to read files outside the configured local storage directory through a path traversal issue in the default LocalStorageBase storage adapter. The issue is authentication-gated and low severity, requires an existing staff account created by an administrator, and no public exploit identified at time of analysis; the vendor fixed it in Ghost 6.27.0.
Server-side request forgery in the Ghost CMS webhooks feature (versions 1.18.0 through releases prior to 6.27.0) allows an authenticated staff user who can create or edit webhooks to point a webhook target_url at internal hosts and force the Ghost server to issue requests to them. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N, score 2.7) confirms this is a network-reachable but privileged-account-required issue whose impact is limited to low confidentiality loss - blind or semi-blind probing rather than response retrieval or code execution - and there is no public exploit identified at time of analysis. Ghost 6.27.0 fixes the issue by routing webhook delivery through a request library that blocks internal IPs unless the operator explicitly opts in via a new configuration flag.
Authenticated Ghost members can read comments and comment replies they are not authorized to access on sites running Ghost 5.9.0 up to (but not including) 6.44.1. The defect is an authorization/input-validation flaw in the comments subsystem (CWE-943) that lets a low-privileged member account reach a code path intended for administrators, disclosing reply content across membership boundaries; the impact is read-only, with no write, post, or availability effect. Vendor-released patch: 6.44.1, and no public exploit identified at time of analysis.
Broken authorization in Ghost CMS versions 5.81.0 through 6.59.x lets an authenticated staff account with the Author role delete posts and pages authored by other users, including through bulk filter-based delete requests. The flaw is a missing primary-author check on the destroy path in the post model's permission logic (CWE-862), rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) - unauthenticated exploitation is not possible, and only multi-author instances with delegated Author accounts are realistically exposed. No public exploit code has been identified at time of analysis and there is no indication the issue has been actively exploited; Ghost fixed the behavior in version 6.60.0.
Authenticated staff holding the Editor or Super Editor role in Ghost CMS versions 0.5.0 through 6.63.x can escalate the privileges of Author and Contributor accounts by assigning their own Editor role to those users through the Ghost Admin API, even though they lack permission to grant that role. The flaw is bounded - attackers can only confer their own Editor-level role and cannot push targets to Administrator or Owner - and exploitation requires an existing, trusted staff account rather than outsider access. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but the vendor released a fix in version 6.64.0, so unpatched, multi-role Ghost publications should upgrade promptly.
Theme translation-file path traversal in Ghost CMS lets an authenticated Administrator read JSON files outside the active theme's directory, potentially exposing server configuration secrets such as database credentials or API keys stored in JSON. All Ghost releases from 1.20.0 up to but not including 6.64.0 are affected, with the fix shipped in 6.64.0; because exploitation requires the highest-privilege Administrator role (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, base 4.9) and yields confidentiality-only impact, this is a low-to-moderate priority issue rather than an anonymous remote attack. No public exploit code has been identified at time of analysis.
Any authenticated staff-level user on a self-hosted Ghost instance running versions 0.7.2 through 6.63.x could infer the relative ordering of other staff users' hashed password values through admin API query options, a low-severity side-channel disclosed as CWE-203 (Observable Discrepancy). The exposure is limited: raw hashes and passwords are never returned, and turning ordering metadata into a usable credential requires substantial additional effort, which is reflected in the CVSS:3.1 base score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) - a trusted staff account is a prerequisite, attack complexity is high, and only low confidentiality impact is assessed. There is no public exploit identified at time of analysis and no indication of active exploitation; the issue is fixed in Ghost 6.64.0 via the upstream PR and commit referenced in the advisory.
Server-side request forgery (SSRF) in Ghost CMS versions 6.0.9 through 6.64.x lets an unauthenticated remote attacker induce the server to issue limited HTTP requests to hosts on its internal network. The flaw is blind - no response body is ever returned to the attacker - so the practical value is confined to request-triggered side effects and liveness/timing inference rather than data exfiltration, and exploitation depends on the target deployment actually having reachable internal hosts (e.g. NAT64/DNS64 setups or flat internal networks). The vendor fixed the issue in Ghost 6.65.0; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, consistent with the assessed CVSS 3.1 score of 4.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N).
Blind server-side request forgery (SSRF) in Ghost CMS versions 6.54.1 through 6.64.x lets an unauthenticated remote attacker coerce the server into issuing limited HTTP requests to hosts on its internal network, using functionality such as the Webmentions feature to submit attacker-controlled URLs that are later fetched by Ghost's oembed/bookmark/favicon pipeline. The impact is constrained: no response body is returned to the attacker, so the attack yields only internal-host reachability probing rather than data exfiltration, and exploitation depends on winning a DNS-rebinding race (AC:H per the assessed vector, overall CVSS 4.0). No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the vendor-released patch is Ghost 6.65.0.
A denial-of-service condition in Ghost CMS affects versions 4.0.0 through 6.66.x, where a crafted content import file can drive catastrophic regular-expression backtracking and pin the Node.js event loop, leaving the server unresponsive. The vulnerability is only reachable by an authenticated Ghost Administrator (CVSS PR:H) who submits a malicious import through the built-in content import feature, so the practical risk is limited to environments where admin credentials are already compromised or misused. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing); vendor-released patch: 6.67.0.
Denial of service in Ghost CMS 5.37.0 through 6.66.x allows an authenticated administrator to pin server CPU and render the Ghost instance unresponsive by sending a crafted request to the external media inliner, which compiles attacker-influenced domain strings into unescaped regular expressions (CWE-1333, inefficient regular expression complexity / catastrophic backtracking). Exploitation requires a Ghost Administrator account (CVSS PR:H, AV:N/AC:L/UI:N/S:U/C:N/I:N/A:H, base score 4.9), so realistic risk is confined to malicious or compromised admin accounts rather than anonymous visitors or the read-only front end. No public exploit identified at time of analysis; the vendor fix is contained in Ghost 6.67.0.
Stored cross-site scripting in Ghost CMS versions 4.0.0 through 6.66.x allows an attacker to plant malicious JavaScript on the victim site's own domain by convincing an Administrator to import a crafted content archive containing an unsanitized SVG image. Per the CVSS vector (AV:N/AC:H/PR:N/UI:R), the attacker does not need credentials but the attack is not self-service: it depends on successful social engineering of a privileged Administrator to run the import (UI:R), and impact on staff users' admin sessions further depends on that stored SVG being rendered in an authenticated admin context. Exploitation is therefore conditional rather than opportunistic, and no public exploit code has been identified at time of analysis (no CISA KEV listing).
Path traversal in Ghost's theme translation loader (CWE-22) lets an authenticated administrator read JSON files outside the active theme directory by tampering with the locale/language setting, potentially exposing server configuration secrets. All Ghost releases from 1.20.0 up to but not including 6.64.0 are affected; the flaw requires a high-privilege admin account (CVSS 4.0 6.9 / assessed CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) and yields read-only disclosure of JSON-format files - no write, no code execution. There is no confirmed active exploitation (CISA KEV not listed) and no public exploit identified at time of analysis; a vendor patch is available in 6.64.0.
Ghost CMS versions from 0.7.2 up to (but not including) 6.64.0 leak password-hash ordering information to authenticated, staff-level users through the Admin API, allowing an insider or a holder of a compromised staff account to learn how other staff members' password hashes are sorted relative to one another. Exploitation requires authenticated staff access with Admin API reachability (PR:L), is rated high complexity (AC:H) because it depends on repeated, carefully crafted queries and the analysis of response discrepancies, and is bounded in impact: per the vendor advisory and independent assessment, the hashes themselves are not disclosed and practical password recovery is not enabled. No public exploit code and no confirmed active exploitation were identified at time of analysis, consistent with the very low CVSS 4.0 score of 2.3 and the assessed CVSS 3.1 vector of AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N.
Privilege escalation in Ghost CMS (TryGhost Ghost) versions 0.5.0 through before 6.64.0 allows an authenticated Editor or Super Editor to assign their own elevated role to other staff accounts, promoting existing Author and Contributor users to Editor or Super Editor without holding the authority to do so. Exploitation is gated by the attacker already holding an Editor or Super Editor account (PR:L in the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, vendor CVSS 4.0 score 5.3), so anonymous outsiders cannot abuse it, and the effect is limited to integrity rather than confidentiality or availability. A vendor-supplied patch is available and no public exploit code has been identified at time of analysis.
Server-side request forgery in Ghost 3.20.2 through 6.50.x allows authenticated staff users to trigger outbound HTTP requests to arbitrary URLs via the image dimension refetching feature. Attackers can point image cards at internal network endpoints or cloud metadata services (e.g., 169.254.169.254) to access resources unavailable from the public internet. No public exploit code identified at time of analysis; the vendor has released a patch in Ghost 6.51.0.
Path traversal in the Ghost CMS ImageSize service (versions 6.14.0 through releases prior to 6.27.0) lets an authenticated staff user with elevated privileges read arbitrary local files from the server outside the intended data/storage directories. Exploitation is network-reachable and requires no user interaction, but is gated behind valid staff credentials, so the impact is bounded to file disclosure (confidentiality only, with no integrity or availability effect). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV), making this a moderate, authentication-gated risk (CVSS 5.1) that the vendor has fixed in Ghost 6.27.0.
Server-side request forgery in Ghost (TryGhost) versions 1.18.0 through 6.27.0 allows an authenticated staff-level user with permission to create or edit webhooks to make the Ghost server send requests to internal network resources, including cloud metadata services. Vendor scoring is CVSS 5.1 with PR:H, reflecting that the attacker must already hold privileged access; no public exploit code was identified at time of analysis and there is no CISA KEV listing.
Cross-site request forgery in the post feedback function of Ghost CMS lets an attacker submit feedback on behalf of any logged-in member who visits a crafted link, affecting versions 5.19.0 up to (but not including) 6.57.1. The attacker needs no account on the target site, but the attack only works against a victim who is an authenticated member with an active session and who follows the malicious page, and the resulting impact is integrity-only - unwanted feedback entries with no confidentiality or availability effect (CVSS 3.1: 5.3). No public exploit code was identified at time of analysis, and the vendor has released a fix in Ghost 6.57.1.
Information disclosure in Ghost CMS affects versions 5.125.1 up to but not including 6.57.1, where the Admin Feedback endpoint omits a proper authorization check and lets an authenticated staff user retrieve member records they should not be able to see. The flaw is credential-gated (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), needs no user interaction, and is limited to confidentiality of member data with no integrity or availability impact, which is why the published 5.3 base score reflects a moderate rather than emergency-level risk. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, so realistic exposure depends mainly on how many staff accounts an instance provisions and how sensitive its member records are.
A race condition in Ghost CMS's staff invitation acceptance flow (affecting versions 0.5.0 through 6.22.x) allows someone holding a valid invitation token to create more than one user account from that single-use invite by firing concurrent acceptance requests before the token is marked consumed. The impact is integrity-only and low (independent assessment: CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, matching the published 5.3), since exploitation is opportunistic rather than deterministic and requires a legitimately issued staff invite token; no public exploit code or confirmed active exploitation was identified at time of analysis. Ghost 6.23.0 contains the vendor fix.
Authenticated low-privilege staff users on Ghost sites can read Admin API keys that should only be visible to higher-privileged accounts, handing them credentials intended for trusted integrations. The exposure affects the Ghost npm package from 3.23.0 through 6.22.x and is resolved in 6.23.0, with the CVSS vector (PR:L, AV:N, no UI) confirming that a valid staff login on a remote instance is the only prerequisite. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the independent assessment rates this as a genuine but modest-severity information-disclosure and privilege-escalation risk driven by insider or compromised-staff scenarios rather than unauthenticated remote attack.
The setup endpoint in Ghost CMS returns the site owner's email address to any remote, unauthenticated visitor, exposing every release from 0.8.0 up to but not including 6.23.0. Exploitation requires no account, no user interaction, and no non-default configuration, but the yield is limited to a single email address - no credentials, content, or system access - so realistic impact is reconnaissance and phishing enablement rather than direct compromise. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and vendor patching is available in 6.23.0.
Unauthenticated attackers can read theme template and metadata files from internet-facing Ghost blogs running any version before 6.20.0 by supplying URL-encoded file paths that slip past the platform's file-extension validation, exposing theme source and configuration but not member data, user records, or site secrets. The flaw requires no special configuration and works against a default installation (CVSS 4.0 base 6.9; independent assessment scores it CVSS 3.1 AV:N/AC:L/PR:N/UI:N with only low confidentiality impact, no integrity or availability impact). No public exploit code has been identified at time of analysis, and the vendor-released fix is Ghost 6.20.0.
Authenticated staff-level users of Ghost CMS (versions 5.42.2 up to but not including 6.58.0) can infer other staff users' password hashes by supplying Admin API bulk post and page edit/delete filters that reference restricted fields such as authors.password. Because the bulk operation code paths fail to reject these restricted-field filters, the match/no-match behaviour acts as a boolean oracle that leaks information about the stored hash, which an attacker can then attack with offline password-guessing (cracking) - it does not hand over credentials directly. This is a genuine but modest-priority authenticated information disclosure (CVSS 5.3, assessed CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, CWE-203); there is no CISA KEV entry and no public exploit identified at time of analysis, and the issue is fully remediated in Ghost 6.58.0.
Unauthenticated visitors to Ghost instances running versions 5.3.0 through 6.57.x in private mode with comments enabled can read comments that private mode should restrict, bypassing the site's privacy settings. This is a low-impact confidentiality flaw limited to comment text disclosure-no write access, account takeover, or integrity impact-and it requires the configuration of private mode plus comments being enabled. Vendor-released patch: 6.58.0; no public exploit identified at time of analysis.
Authenticated low-privilege staff users on Ghost CMS versions 4.3.0 through 6.57.x can abuse staff tokens to modify posts beyond the permissions granted to their role, effectively bypassing the post-editing restrictions that separate Authors and Contributors from higher-privileged editors. Exploitation requires a valid, already-provisioned staff account (PR:L in both the reported and independently assessed vectors), so it is not reachable by anonymous internet users, and the impact is confined to unauthorized content modification (integrity) with no data disclosure or availability loss. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is a moderate, authenticated-only authorization flaw rather than a widespread-exploitation priority; a vendor patch is available from Ghost in version 6.58.0.
Authenticated Ghost site members on versions 5.3.0 through 6.61.x can retrieve the post excerpts (preview snippets) of gated, members-only or premium posts they are not entitled to read, because the excerpts endpoint fails to enforce the same access checks applied to full post content. The exposure is limited to excerpt text rather than complete article bodies, so the practical impact is partial content disclosure, and sites that publish no gated or paywalled content are unaffected. Any registered member account - including a free-tier member with no subscription - is sufficient to trigger the issue; no public exploit code has been identified at time of analysis, and no confirmed active exploitation (CISA KEV) has been reported.
Staff invite acceptance in Ghost before 6.62.0 allows the holder of a valid invite token to create their account with an arbitrary, attacker-chosen email address instead of the address the invite was issued to, breaking the binding between an invited identity and the resulting staff account. Exploitation is authenticated (CVSS PR:L) and depends on a legitimate invite token already existing and having been leaked, forwarded, or otherwise exposed - a remote unauthenticated attacker cannot mint an invite and trigger this on their own - and the assessed impact is integrity-only with no confidentiality or availability loss (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), making this a low-to-moderate risk issue despite the 'authentication bypass' label. No public exploit identified at time of analysis; the vendor has released a fix in Ghost 6.62.0.
Blind password hash disclosure in Ghost Admin API versions prior to 6.54.1 allows any authenticated staff-level user to retrieve hashed passwords of other staff accounts by crafting filtered API queries against the posts or pages browse endpoints. The root cause is insufficient field-level access control in MongoDB filter queries, exposing internal authentication fields (CWE-200). No active exploitation is confirmed (not in CISA KEV), and downstream account takeover is partially mitigated by Ghost's Device Verification and email MFA features, though the hash disclosure itself is confirmed and unambiguously fixed in 6.54.1.
Cross-site scripting in Ghost CMS (versions 5.26.0 through 6.54.0) allows a high-privileged administrator to plant arbitrary JavaScript via the Universal Import feature, which fails to sanitize the `feature_image_caption` field and link card URLs before storing and rendering them. The fix in v6.54.1 introduces DOMPurify sanitization across both the Ember-based admin post history modal and the Node.js frontend rendering pipeline, alongside a strict URL protocol allowlist in the JSON-to-HTML importer. No active exploitation is confirmed (not in CISA KEV) and no public proof-of-concept is known; the high-privilege prerequisite substantially limits the realistic attacker pool.
Server-side request forgery (SSRF) filter bypass in Ghost CMS 6.0.9 through 6.21.0 allows remote unauthenticated attackers to direct the application to reach internal network services by supplying IPv6 literals that map to private IPv4 addresses, circumventing Ghost's outbound IP blocklist. The root cause is CWE-184 (Incomplete List of Disallowed Inputs): the filter validates against RFC 1918 private ranges but does not normalize IPv6-mapped IPv4 notation before comparison. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists; Ghost 6.21.1 resolves the issue.
DNS rebinding bypasses Ghost CMS's private-IP validation for outbound HTTP requests, enabling server-side request forgery (SSRF) against internal network resources. Versions 6.0.9 through 6.21.0 are affected; the root cause is a TOCTOU race (CWE-367) between Ghost's allowlist check and the actual TCP connection, which a DNS-rebinding attacker exploits by switching DNS records between check-time and connect-time. No public exploit code identified and not listed in CISA KEV, but the scope-changed CVSS rating (S:C) reflects that successful exploitation escapes Ghost's network boundary into adjacent internal infrastructure.
Server-side request forgery in Ghost CMS versions 6.19.4 through 6.21.1 allows authenticated staff users to pivot the Ghost server into making arbitrary outbound HTTP requests, including to internal network hosts and cloud instance metadata endpoints. The vulnerable code path is Ghost's post re-rendering pipeline, which fetches image dimensions from URLs stored in image cards without validating those URLs against a trusted host allowlist. No public exploit has been identified at time of analysis, and a vendor-released patch is available in 6.21.1.
Ghost CMS versions 5.18.0 through 6.21.1 expose registered member email addresses to unauthenticated enumeration via observable discrepancies in the members signin endpoint responses. Any Ghost site with the members feature active is affected, allowing an attacker to silently probe whether arbitrary email addresses belong to site subscribers. No public exploit or active exploitation (CISA KEV) has been identified; vendor patch is available in 6.21.1.
Stored cross-site scripting in Ghost CMS (versions 6.19.4 through 6.21.0) is enabled by the Admin API file upload endpoint accepting and preserving attacker-supplied Content-Type headers without server-side validation. When Ghost is configured with S3 or GCS storage backends that serve uploaded files from the same origin as the site, an authenticated attacker can upload a file with a crafted Content-Type (e.g., text/html) that causes browsers to execute it as HTML or JavaScript, enabling stored XSS against visitors and staff. No public exploit code has been identified at time of analysis, and the vulnerability is fixed in Ghost 6.21.1.
Filter validation bypass in Ghost CMS public API endpoints exposes private fields - including password hashes - to unauthenticated remote attackers via repeated brute-force probing. Instances running SQLite are most severely impacted: full password hashes are recoverable, enabling offline cracking. MySQL-backed instances leak structurally degraded hashes (case information lost), which the vendor assesses would render subsequent cracking attempts fruitless. No public exploit code exists and the vulnerability is not in CISA KEV at time of analysis, but the unauthenticated, network-accessible nature of the flaw lowers the bar for opportunistic discovery.
Ghost is a Node.js content management system. In versions 5.38.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost’s media inliner mechanism allows staff users in possession of a valid authentication token for the Ghost Admin API to exfiltrate data from internal systems via SSRF. [CVSS 2.7 LOW]
SQL injection in Ghost's Admin API members/events endpoint enables authenticated administrators to execute arbitrary database queries, affecting versions 5.90.0-5.130.5 and 6.0.0-6.10.3. An attacker with valid Admin API credentials could exploit this to extract, modify, or delete sensitive data stored in the Ghost database. Patches are available in versions 5.130.6 and 6.11.0.
Server-Side Request Forgery (SSRF) vulnerability in Ghost allows an attacker to access internal resources.0.0 through 6.0.8, from 5.99.0 through 5.130.3. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Ghost is a Node.js content management system. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Ghost through 5.85.1 allows remote attackers to bypass an authentication rate-limit protection mechanism by using many X-Forwarded-For headers with different values. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Ghost before 5.82.0 allows CSV Injection during a member CSV export. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Ghost through 5.76.0 allows stored XSS, and resultant privilege escalation in which a contributor can take over any account, via an SVG profile picture that contains JavaScript code to interact with. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Ghost before 5.76.0 allows XSS via a post excerpt in excerpt.js. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Cross-Site Scripting (XSS) vulnerability could allow attackers to inject malicious scripts into web pages viewed by other users.
Ghost is an open source content management system. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Ghost is an app for new-media creators with tools to build a website, publish content, send newsletters, and offer paid subscriptions to members. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Exposure of Sensitive Information vulnerability could allow attackers to access sensitive data that should not be disclosed.
Ghost before 5.42.1 allows remote attackers to read arbitrary files within the active theme's folder via /assets/built%2F..%2F..%2F/ directory traversal. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Ghost 5.35.0 allows authorization bypass: contributors can view draft posts of other users, which is arguably inconsistent with a security policy in which a contributor's draft can only be read by. Rated medium severity (CVSS 5.7), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A user enumeration vulnerability exists in the login functionality of Ghost Foundation Ghost 5.9.4. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An authentication bypass vulnerability exists in the newsletter subscription functionality of Ghost Foundation Ghost 5.9.4. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
An arbitrary file upload vulnerability in the file upload module of Ghost CMS v4.42.0 allows attackers to execute arbitrary code via a crafted file. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An arbitrary file upload vulnerability in the file upload module of Ghost v4.39.0 allows attackers to execute arbitrary code via a crafted SVG file. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Ghost is a Node.js content management system. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Ghost is a Node.js CMS. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable, no authentication required. Public exploit code available and no vendor patch available.