- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 12
- Public CVEs
- 33
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays from $1,500
- for critical bugs.
- Report on Sorona
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Sorona lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical | $1,500+ | |
| High | $700+ | |
| Medium | $300+ | |
| Low |
|
$100 $100 / 1 month Claude Max |
- Safe harbor
-
Partial
Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.
- Hall of fame
-
Yes
The Ghost Foundation offers a public acknowledgement for any report that results in a security commit and nothing beyond that
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
12 assets you may test, 6 excluded.
Web 1
- https://ghost.org
Products and areas 11
- Email sending and newsletter delivery, covering recipient selection and anything that renders into an outgoing message
- File and image upload, storage and the routes that serve uploaded content back
- Import and export routines, which parse an operator-supplied archive and write directly into the content store
- Integrations, webhooks and the API key model behind them
- Staff accounts, the role model above them, and the invitation flow that creates new ones
- The Admin API in full, along with the session and token handling that gates it
- The Content API and the keys that decide which posts an anonymous request can read, including drafts and member-only content
- Theme handling and the template rendering layer, including theme upload, validation and activation
- The members system end to end: signup, sign-in tokens, the member session, and every member-facing endpoint on a public site
- The published policy asks for any vulnerability in Ghost through the security address or a GitHub advisory, and names exactly one carve-out. Beyond that it draws no boundary around the codebase
- The setup, update and migration paths, which run with more authority than the running site
Out of scope (6)
- Deployment configuration: reverse-proxy setup, mail credentials and storage adapters the operator chose
- Findings that need an administrator account already in hand, since a full administrator sits inside the trust boundary by design
- Privilege escalation as a result of trusted users publishing arbitrary JavaScript, the one exclusion the policy names outright
- Reports filed on hackerone.com/ghost, which is an unrelated researcher's profile rather than a Ghost program
- Third-party themes and integrations that are not part of the Ghost repository
- Upstream Node and library defects, unless Ghost's own use of them is what makes the issue reachable
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.
While testing
-
Submit through sorona.xyz.
-
Report to the address on the policy page , the address SECURITY.md and docs.ghost.org/security both publish.
-
GitHub private vulnerability reporting is also enabled on TryGhost/Ghost
-
Report against a current release and say whether the finding needs a staff account, a member account or neither
Not accepted
-
Privilege escalation as a result of trusted users publishing arbitrary JavaScript
-
Third-party themes and integrations that are not part of the Ghost repository
-
Upstream Node and library defects, unless Ghost's own use of them is what makes the issue reachable
-
Deployment configuration: reverse-proxy setup, mail credentials and storage adapters the operator chose
-
Findings that need an administrator account already in hand
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-29784 | Ghost is a Node.js content management system. From version 5.101.6 to 6.19.2, incomplete CSRF protections around /session/verify made it possible to use OTCs in login sessions different from the requesting session. In some scenarios this might have made it easier for phishers to take over a Ghost site. This issue has been patched in version 6.19.3. | High 7.5 | 7 Mar 2026 |
| CVE-2026-29053 | Ghost is a Node.js content management system. From version 0.7.2 to 6.19.0, specifically crafted malicious themes can execute arbitrary code on the server running Ghost. This issue has been patched in version 6.19.1. | High 7.6 | 5 Mar 2026 |
| CVE-2026-26980 | Ghost is a Node.js content management system. Versions 3.24.0 through 6.19.0 allow unauthenticated attackers to perform arbitrary reads from the database. This issue has been fixed in version 6.19.1. | Critical 9.4 | 20 Feb 2026 |
| CVE-2026-24778 | Ghost is an open source content management system. In Ghost versions 5.43.0 through 5.12.04 and 6.0.0 through 6.14.0, an attacker was able to craft a malicious link that, when accessed by an authenticated staff user or member, would execute JavaScript with the victim's permissions, potentially leading to account takeover. Ghost Portal versions 2.29.1 through 2.51.4 and 2.52.0 through 2.57.0 were v | High 8.8 | 27 Jan 2026 |
| CVE-2026-22595 | Ghost is a Node.js content management system. In versions 5.121.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost's handling of Staff Token authentication allowed certain endpoints to be accessed that were only intended to be accessible via Staff Session authentication. External systems that have been authenticated via Staff Tokens for Admin/Owner-role users would have had acces | High 8.1 | 10 Jan 2026 |
| CVE-2026-22596 | Ghost is a Node.js content management system. In versions 5.90.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost's /ghost/api/admin/members/events endpoint allows users with authentication credentials for the Admin API to execute arbitrary SQL. This issue has been patched in versions 5.130.6 and 6.11.0. | Medium 6.7 | 10 Jan 2026 |
| CVE-2026-22597 | 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. This issue has been patched in versions 5.130.6 and 6.11.0. | Medium 5.1 | 10 Jan 2026 |
| CVE-2026-22594 | Ghost is a Node.js content management system. In versions 5.105.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost's 2FA mechanism allows staff users to skip email 2FA. This issue has been patched in versions 5.130.6 and 6.11.0. | High 8.1 | 10 Jan 2026 |
| CVE-2025-9862 | Server-Side Request Forgery (SSRF) vulnerability in Ghost allows an attacker to access internal resources.This issue affects Ghost: from 6.0.0 through 6.0.8, from 5.99.0 through 5.130.3. | Medium 6.1 | 17 Sep 2025 |
| CVE-2024-43409 | Ghost is a Node.js content management system. Improper authentication on some endpoints used for member actions would allow an attacker to perform member-only actions, and read member information. This security vulnerability is present in Ghost v4.46.0-v5.89.4. v5.89.5 contains a fix for this issue. | Medium 6.5 | 20 Aug 2024 |
| CVE-2024-34451 | 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. NOTE: the vendor's position is that Ghost should be installed with a reverse proxy that allows only trusted X-Forwarded-For headers. | Critical 9.1 | 16 Jun 2024 |
| CVE-2024-34448 | Ghost before 5.82.0 allows CSV Injection during a member CSV export. | High 8.8 | 22 May 2024 |
| CVE-2024-23724 | 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 the API on localhost TCP port 3001. NOTE: The discoverer reports that "The vendor does not view this as a valid vector." | Critical 9.0 | 11 Feb 2024 |
| CVE-2024-23725 | Ghost before 5.76.0 allows XSS via a post excerpt in excerpt.js. An XSS payload can be rendered in post summaries. | Medium 6.1 | 21 Jan 2024 |
| CVE-2023-40028 | Ghost is an open source content management system. Versions prior to 5.59.1 are subject to a vulnerability which allows authenticated users to upload files that are symlinks. This can be exploited to perform an arbitrary file read of any file on the host operating system. Site administrators can check for exploitation of this issue by looking for unknown symlinks within Ghost's `content/` folder. | Medium 4.9 | 15 Aug 2023 |
| CVE-2023-31133 | Ghost is an app for new-media creators with tools to build a website, publish content, send newsletters, and offer paid subscriptions to members. Prior to version 5.46.1, due to a lack of validation when filtering on the public API endpoints, it is possible to reveal private fields via a brute force attack. Ghost(Pro) has already been patched. Maintainers can find no evidence that the issue was ex | High 7.5 | 8 May 2023 |
| CVE-2023-32235 | 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. This occurs in frontend/web/middleware/static-theme.js. | High 7.5 | 5 May 2023 |
| CVE-2020-24736 | Buffer Overflow vulnerability found in SQLite3 v.3.27.1 and before allows a local attacker to cause a denial of service via a crafted script. | Medium 5.5 | 11 Apr 2023 |
| CVE-2022-43441 | A code execution vulnerability exists in the Statement Bindings functionality of Ghost Foundation node-sqlite3 5.1.1. A specially-crafted Javascript file can lead to arbitrary code execution. An attacker can provide malicious input to trigger this vulnerability. | High 8.1 | 16 Mar 2023 |
| CVE-2023-26510 | 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 editors until published by an editor. NOTE: the vendor's position is that this behavior has no security impact. | Medium 5.7 | 5 Mar 2023 |
| CVE-2022-47197 | An insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. Default installations of Ghost allow non-administrator users to inject arbitrary Javascript in posts, which allow privilege escalation to administrator via XSS. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into | Medium 5.4 | 19 Jan 2023 |
| CVE-2022-47194 | An insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. Default installations of Ghost allow non-administrator users to inject arbitrary Javascript in posts, which allow privilege escalation to administrator via XSS. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into | Medium 5.4 | 19 Jan 2023 |
| CVE-2022-47195 | An insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. Default installations of Ghost allow non-administrator users to inject arbitrary Javascript in posts, which allow privilege escalation to administrator via XSS. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into | Medium 5.4 | 19 Jan 2023 |
| CVE-2022-47196 | An insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. Default installations of Ghost allow non-administrator users to inject arbitrary Javascript in posts, which allow privilege escalation to administrator via XSS. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into | Medium 5.4 | 19 Jan 2023 |
| CVE-2022-41654 | An authentication bypass vulnerability exists in the newsletter subscription functionality of Ghost Foundation Ghost 5.9.4. A specially-crafted HTTP request can lead to increased privileges. An attacker can send an HTTP request to trigger this vulnerability. | Medium 4.3 | 22 Dec 2022 |
| CVE-2022-41697 | A user enumeration vulnerability exists in the login functionality of Ghost Foundation Ghost 5.9.4. A specially-crafted HTTP request can lead to a disclosure of sensitive information. An attacker can send a series of HTTP requests to trigger this vulnerability. | Medium 5.3 | 22 Dec 2022 |
| CVE-2022-21227 | The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. If passed an invalid Function object it will throw and crash the V8 engine. | High 7.5 | 1 May 2022 |
| CVE-2022-28397 | 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. NOTE: Vendor states as detailed in Ghost's security documentation, files can only be uploaded and published by trusted users, this is intentional. | Critical 9.8 | 12 Apr 2022 |
| CVE-2022-27139 | 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. NOTE: Vendor states that as outlined in Ghost's security documentation, upload of SVGs is only possible by trusted authenticated users. The uploading of SVG files to Ghost does not represent a remote code execution vulnerability. SVGs are not executab | Critical 9.8 | 12 Apr 2022 |
| CVE-2021-39192 | Ghost is a Node.js content management system. An error in the implementation of the limits service between versions 4.0.0 and 4.9.4 allows all authenticated users (including contributors) to view admin-level API keys via the integrations API endpoint, leading to a privilege escalation vulnerability. This issue is patched in Ghost version 4.10.0. As a workaround, disable all non-Administrator accou | Medium 6.5 | 3 Sep 2021 |
| CVE-2021-29484 | Ghost is a Node.js CMS. An unused endpoint added during the development of 4.0.0 has left sites vulnerable to untrusted users gaining access to Ghost Admin. Attackers can gain access by getting logged in users to click a link containing malicious code. Users do not need to enter credentials and may not know they've visited a malicious site. Ghost(Pro) has already been patched. We can find no evide | Medium 6.8 | 29 Apr 2021 |
| CVE-2020-8134 | Server-side request forgery (SSRF) vulnerability in Ghost CMS < 3.10.0 allows an attacker to scan local or external network or otherwise interact with internal systems. | High 8.1 | 20 Mar 2020 |
| CVE-2016-10983 | The ghost plugin before 0.5.6 for WordPress has no access control for wp-admin/tools.php?ghostexport=true downloads of exported data. | Medium 6.5 | 17 Sep 2019 |
Original policy
Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 18 Last 12 months Access control 35 % XSS 25 % Auth/session 20 % Info disclosure 20 % Latest advisories Loading the feed Overview Ghost is the Node publishing platform behind a large share of independent media sites and paid newsletters, at 378 million Docker pulls and roughly 0.1% of all websites. Most installs are self-hosted, so the operator's audience list and their staff accounts sit on the same box as the public site. Eighteen advisories landed in the last twelve months, two of them critical, including CVE-2026-53943, and a seven-advisory batch went out on a single day in June. The Ghost Foundation offers a public acknowledgement for any report that results in a security commit and nothing beyond that, so sorona.xyz pays you directly on qualified, reproduced findings. In scope The published policy asks for any vulnerability in Ghost through the security address or a GitHub advisory, and names exactly one carve-out. Beyond that it draws no boundary around the codebase The Admin API in full, along with the session and token handling that gates it The Content API and the keys that decide which posts an anonymous request can read, including drafts and member-only content The members system end to end: signup, sign-in tokens, the member session, and every member-facing endpoint on a public site Staff accounts, the role model above them, and the invitation flow that creates new ones Theme handling and the template rendering layer, including theme upload, validation and activation File and image upload, storage and the routes that serve uploaded content back Import and export routines, which parse an operator-supplied archive and write directly into the content store Email sending and newsletter delivery, covering recipient selection and anything that renders into an outgoing message Integrations, webhooks and the API key model behind them The setup, update and migration paths, which run with more authority than the running site Out of scope Privilege escalation as a result of trusted users publishing arbitrary JavaScript, the one exclusion the policy names outright Third-party themes and integrations that are not part of the Ghost repository Upstream Node and library defects, unless Ghost's own use of them is what makes the issue reachable Deployment configuration: reverse-proxy setup, mail credentials and storage adapters the operator chose Reports filed on hackerone.com/ghost, which is an unrelated researcher's profile rather than a Ghost program Findings that need an administrator account already in hand, since a full administrator sits inside the trust boundary by design Most-valued findings Unauthenticated access to the Admin API, or anything that produces a staff session without credentials. Two of the eighteen advisories in the window reached critical, CVE-2026-53943 and CVE-2026-26980, and this is the shape with the highest ceiling Content API key handling that returns drafts, scheduled posts or member-only content to an anonymous request, since paywalled content is the operator's revenue Member identity defects: a sign-in flow that binds a session to the wrong member, or a token that survives revocation. On a paid newsletter the member list is the whole business Staff privilege escalation between roles, contributor upward, which is exactly the escalation the trusted-user JavaScript exclusion does not cover Stored cross-site scripting that fires for a staff user without passing through the publishing path the policy excludes, for example through a member-supplied field or an integration payload Theme upload and rendering reaching server-side execution or arbitrary file read, since theme activation is a routine administrative action Server-side request forgery out of any outbound fetch, including webhook delivery and remote content retrieval Import and export handling of an attacker-supplied archive, which writes into the content store with the site's own authority Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report to [email protected] , the address SECURITY.md and docs.ghost.org/security both publish. GitHub private vulnerability reporting is also enabled on TryGhost/Ghost ghost.org publishes no security.txt. The documentation page is the policy The reward is a public acknowledgement for any report that leads to a security commit. Nothing else is offered Privilege escalation achieved by a trusted user publishing arbitrary JavaScript is excluded by name, so a finding that relies on an author or editor injecting script into a post will be closed The ghost handle on HackerOne is a researcher's user profile rather than a Ghost program. There is no Ghost team on any platform Report against a current release and say whether the finding needs a staff account, a member account or neither Disclosure Coordinated by email or through the GitHub advisory flow and published as a GHSA on TryGhost/Ghost alongside a patched release. Publication runs in batches tied to releases, with seven advisories landing on 10 June 2026, so the practical embargo is set by the next security release rather than by a published day count. The commitment is a public acknowledgement once the fix has shipped. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability