CVE-2026-105651 TryGhost CVE debrief

Who should care

Defenders responsible for Ghost deployments, particularly those with staff users who have Contributor roles, should assess exposure and prioritize upgrading to version 6.64.0 or later.

Why it matters

CVE-2026-105651 is a high-severity vulnerability in Ghost that allows staff users to store malicious content, potentially leading to XSS attacks and compromise of admin sessions. Defenders should prioritize upgrading to version 6.64.0 or later and monitor staff user activity.

• Potential compromise of staff users' admin sessions
• Stored XSS attacks via bookmark card images
• Elevation of privileges for malicious staff users

Technical summary

Ghost, a Node.js content management system, is vulnerable to stored XSS attacks via bookmark card images. From version 5.94.0 to 6.64.0, staff users could store non-image files as bookmark icons or thumbnails, potentially leading to compromise of other staff users' admin sessions. The vulnerability allows staff users to host arbitrary HTML on the site's domain. Defenders should prioritize upgrading to Ghost version 6.64.0 or later to prevent potential XSS attacks. Staff users with Contributor roles should be aware of the risks associated with creating bookmark cards. The issue is fixed in version 6.64.0, and defenders should review and monitor staff user activity for suspicious bookmark card creation.

Defensive priority

Defenders should prioritize upgrading to Ghost version 6.64.0 or later to prevent potential XSS attacks. Staff users with Contributor roles should be aware of the risks associated with creating bookmark cards.

Recommended defensive actions

• Upgrade to Ghost version 6.64.0 or later
• Review and monitor staff user activity for suspicious bookmark card creation
• Implement additional security measures to prevent XSS attacks
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and fixed version. However, there is limited information on potential exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.