GhostCMS
CVE-2026-29053
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGhost 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGhost CMS versions 0.7.2 through 6.19.0 contain a critical vulnerability where specifically crafted malicious themes can achieve arbitrary code execution on the server. The vulnerability stems from insufficient sanitization/validation of theme files during the theme parsing or installation process, allowing attackers to inject and execute arbitrary commands through theme components.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GhostCMS
>= 0.7.2, < 6.19.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Ghost versionRun 'ghost version' in the Ghost installation directory, or check the package.json file for the 'ghost' dependency versionAffected if The version is >= 0.7.2 and < 6.19.1
-
Verify theme installation capability is activeCheck if the /ghost/api/admin/themes endpoint is accessible or if theme upload functionality is enabled in the admin panel settingsAffected if Theme upload/installation is permitted (default state in Ghost)
-
Identify installed themesList contents of the /content/themes/ directory, or query the themes database tableAffected if Any custom or third-party themes are present in the installation
-
Inspect theme files for suspicious codeReview theme .hbs template files and any .js files within the theme folder for base64 decode, child_process, exec, eval, or shell command patternsAffected if Theme files contain obfuscated code, unusual shell execution calls, or encoded commands that were not intentionally added
You are affected if Ghost version is 0.7.2 or higher but below 6.19.1 AND theme upload/installation from untrusted sources has been performed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.19.1
Immediately upgrade Ghost to version 6.19.1 or later. Until patched, avoid installing themes from untrusted sources and audit existing themes for malicious code.
6.19.1
- Upgrade Ghost to version 6.19.1 or later to remediate the arbitrary code execution vulnerability via malicious themes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ghost
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29053 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data