CVE-2026-103288: Ghost: Authorization Bypass in Comment Like Feature
Ghost 5.9.0 up to 6.44.1 has an authorization bypass in the comment like feature. A logged-in member can delete likes or dislikes on comments that they are not allowed to remove. The vendor fixed it in Ghost 6.44.1. Sites with member comments enabled should update.
Published Oct 27, 2026 · Analysis Nov 1, 2026
What an attacker can do
Ghost's comments feature lets members like and dislike comments, and remove their own votes. The advisory says an input validation issue allowed members to delete comment likes and dislikes they were not authorized to delete. The assigned weakness is CWE-943, improper neutralization in data query logic, which fits a lookup that is built from caller input without enough checks.
The attacker needs a member account on the site, which on a site with open sign-up is easy to get. There is no user interaction. The effect is on integrity only: vote counts can be altered by removing other members' reactions. The advisory reports no data exposure, no account takeover and no code execution.
The linked fix, pull request 28297, reworks comment lookups in the comments service so that write actions such as vote removal check comment visibility through one consolidated lookup. Its page does not name the exact route or describe the validation change, so the precise request shape is not in the sources. Publishers who run public comment sections are the ones affected.
Who is affected
Affected: Ghost from 5.9.0 up to but not including 6.44.1. Sites are exposed in practice only if members can comment and react to comments.
For a Ghost-CLI install, check the version:
ghost versionFor Docker, check the image tag you run, for example with docker inspect on the container's image. The admin interface also shows the version in its About screen.
ghost
- Ecosystem
- npm
- Affected
- >= 5.9.0, < 6.44.1
- Fixed in
- 6.44.1
- Check
npm ls ghost
How to fix it
Update to Ghost 6.44.1, which contains the fix.
For a Ghost-CLI install:
ghost updateFor Docker, pull the current official Ghost image and recreate the container. The vendor documents both update paths. The sources name no workaround. If you cannot update right away, you can turn off member comments in the Ghost settings until you do.
How to tell if you were hit
Compare comment vote counts with the member-level reaction records in your database for comments that lost likes or dislikes without the owning member acting. Check access logs for requests that remove a comment like or dislike from sessions whose member did not create the vote.
The advisory gives no log signature, so the most reliable check is the vote table itself: look for removed votes concentrated on a few comments or members, or complaints from members that their reactions disappeared.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
An input validation issue allowed members to delete comment likes / dislikes that they were not authorized to delete.
Vulnerable versions
This vulnerability is present in Ghost from v5.9.0 up to v6.44.1.
Patches
v6.44.1 contains a fix for this issue.
How to update
For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.
If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.
References
Ghost thanks Adel Assakaf and Arthur Gurunlian as well as Geoffrey Diederichs of Escape for disclosing this vulnerability responsibly.
For more information
If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected]).
Credited to assakafpix, Buggs777.
Questions
- Which Ghost version fixes CVE-2026-103288?
Ghost 6.44.1. Versions from 5.9.0 up to that release are affected.
- Does the attacker need to be an admin?
No. A member account is enough, and the vector shows low privileges and no user interaction.
- What can the attacker actually do?
Delete comment likes or dislikes they should not be able to delete. The advisory describes an integrity effect on votes only, with no data leak or code execution.
- Is it exploited in the wild?
No source reports exploitation, and it is not in CISA's KEV catalog.
References
Read for this analysis:
- https://github.com/TryGhost/Ghost/security/advisories/GHSA-qrh6-cwg3-343x
- https://nvd.nist.gov/vuln/detail/CVE-2026-103288
- https://github.com/TryGhost/Ghost/commit/405c2623ff9060295d4a87d3a0eb4ef766c8d2d3
- https://github.com/TryGhost/Ghost/releases/tag/v6.44.1
- https://www.vulncheck.com/advisories/ghost-5.9.0-before-6.44.1-authorization-bypass-via-comment-like
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-105642
Ghost: Remote Code Execution via Bookmark Card Images
high8.8Oct 7, 2026CVE-2026-105643
Ghost: Stored XSS via Embed Card Previews
high7.3Oct 7, 2026CVE-2026-105644
Ghost : Stored XSS via SVG Files in Content Imports
medium6.8Oct 7, 2026CVE-2026-105645
Ghost: Regular Expression Denial of Service in External Media Inliner
medium4.9Oct 7, 2026CVE-2026-105646
Ghost: Regular Expression Denial of Service in Content Import
medium4.9Oct 7, 2026CVE-2026-105647
Ghost: Server-Side Request Forgery in Bookmark Fetching
medium4.0Oct 7, 2026
