Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
Ghost is a Node.js content management system. From until 6.37.0, when Ghost is behind a shared caching layer that results in cached content being shared between different visitors, an unauthenticated user could send an x-ghost-preview header that altered the rendered frontend response. In affected cache configurations, that response could be stored and served to subsequent visitors requesting the same page, allowing cache poisoning of request-specific preview output. When running Ghost's frontend and admin panel on the same domain this could be used to take over staff user accounts. When running these on different domains staff accounts have no exposure. This vulnerability is fixed in 6.37.0.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE
Here's the writeup for CVE-2026-53943, a cache poisoning -> XSS vuln I found in Ghost CMS 👻 https://cryptocat.me/blog/research/analysis/cve_2026_53943/
Post summary
The post announces a writeup detailing a cache‑poisoning XSS vulnerability (CVE-2026-53943) in Ghost CMS, directing readers to a blog for full analysis.
CVE-2026-53943 is live. If you run npm ghost, read this now. Ghost: Cache-poisoning XSS in Ghost frontend via x-ghost-preview header New week. Sharper than the last.
Post summary
The post alerts that CVE-2026-53943 is currently live, describing it as a cache‑poisoning XSS vulnerability in Ghost’s frontend triggered by the `x-ghost-preview` header, but it provides no PoC, exploit code, or patch information.
🔴 Ghost CMS, Cache-Poisoning XSS, #CVE-2026-53943 (Critical) -DC-Jul2026-821 https://dailycve.com/ghost-cms-cache-poisoning-xss-cve-2026-53943-critical-dc-jul2026-821/
Post summary
The tweet announces a new critical cache‑poisoning XSS vulnerability (CVE‑2026‑53943) in Ghost CMS and points to a source for further details.