GHSA-65P7-PJJ8-GGMR

Member account takeover

Workarounds

The patch in 4.15.1 and 3.42.6 adds a new authenticated endpoint for updating member email addresses. Updating Ghost is the quickest complete solution.

As a workaround, if for any reason you cannot update your Ghost instance, you can block the POST /members/api/send-magic-link/ endpoint, which will also disable member login and signup for your site.

For more information

If you have any questions or comments about this advisory:

• Email us at [email protected]

An error in the implementation of the member email change functionality allows unauthenticated users to change the email address of arbitrary member accounts to one they control by crafting a request to the relevant API endpoint, and validating the new address via magic link sent to the new email address.

Ghost(Pro) has already been patched. Self-hosters are impacted if running Ghost a version between 3.18.0 and 4.15.0 with members functionality enabled.

GHSA-65P7-PJJ8-GGMR has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.42.6, 4.15.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Fixed in 4.15.1, all 4.x sites should upgrade as soon as possible.
Fixed in 3.42.6, all 3.x sites should upgrade as soon as possible.

1. What is GHSA-65P7-PJJ8-GGMR? GHSA-65P7-PJJ8-GGMR is a medium-severity security vulnerability in ghost (npm), affecting versions >= 3.18.0, < 3.42.6. It is fixed in 3.42.6, 4.15.1.
2. How severe is GHSA-65P7-PJJ8-GGMR? GHSA-65P7-PJJ8-GGMR has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ghost are affected by GHSA-65P7-PJJ8-GGMR? ghost (npm) versions >= 3.18.0, < 3.42.6 is affected.
4. Is there a fix for GHSA-65P7-PJJ8-GGMR? Yes. GHSA-65P7-PJJ8-GGMR is fixed in 3.42.6, 4.15.1. Upgrade to this version or later.
5. Is GHSA-65P7-PJJ8-GGMR exploitable, and should I be worried? Whether GHSA-65P7-PJJ8-GGMR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-65P7-PJJ8-GGMR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-65P7-PJJ8-GGMR?
   • Upgrade ghost to 3.42.6 or later
   • Upgrade ghost to 4.15.1 or later

Other vulnerabilities in ghost