TryGhost Ghost CMS · Public exploit code

PoC emerges for two remote code execution flaws in Ghost CMS

· 1 min read

Two remote code execution flaws affect TryGhost's Ghost CMS: CVE-2026-105642 lets a staff user, including a Contributor, trigger memory corruption through a specially crafted SVG image, and CVE-2026-105677 lets an Administrator run arbitrary JavaScript through malicious theme translation directories. According to ptdbugs, a PoC has been discovered for both flaws, which allow command execution with the privileges of the Ghost server process. The source cites no fix; restrict low-privilege staff accounts and limit Administrators until a patch is released.

Illustration: PoC emerges for two remote code execution flaws in Ghost CMS
WhatsApp LinkedIn X
HighVulnerabilityPublic exploit codeFix unconfirmed

In 30 seconds

Alleged

A proof-of-concept exploit has reportedly surfaced for two remote code execution flaws in Ghost CMS, the publishing platform from TryGhost. Remote code execution means an attacker can run commands on the server itself. The researcher known as ptdbugs says the PoC covers CVE-2026-105642, a memory corruption bug in image processing that even a low-privilege Contributor account could trigger with a crafted SVG file, and CVE-2026-105677, which reportedly lets an Administrator run arbitrary JavaScript through theme translation directories. Both paths are said to end with commands running at the privilege level of the Ghost server process. No fix is mentioned in the report.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

What happened

Observed

The disclosure came through a post on X by ptdbugs, a vulnerability research account, announcing that a PoC, short for proof-of-concept, has been discovered for the two flaws. The report carries the tracking ID PT-2026-106138 and is indexed on the dbu.gs vulnerability tracker. Vendor is listed as TryGhost and product as Ghost CMS.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Alleged

According to the report, the two vulnerabilities sit in different corners of the platform. One affects bookmark card image processing, where a specially crafted SVG image triggers memory corruption, corruption of the server's working memory that can be steered into code execution. The other affects theme translation loading, where malicious translation directories loaded by an Administrator execute arbitrary JavaScript when the feature is enabled.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Observed

The advisory trail also includes a public GitHub repository named CVE-2026-105642-POC under the account fixedbyreboot, which surfaced alongside the advisory feed and points to where the exploit code for the first flaw is being shared. The contents of that repository were not retrieved in this batch, so what it actually demonstrates remains unverified.github.comgithub.com · rssOpen original sourceSee in source list

Why it matters

Inferred

The Contributor angle is the alarming part. Contributor is one of the least trusted roles in Ghost, typically limited to drafting posts. If the report holds, someone with that small a foothold could reach memory corruption and from there potentially full command execution on the server. The distance between draft access and server control collapses to a single uploaded image.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Inferred

The reported landing zone matters too. Commands running with the privileges of the Ghost server process could expose the hosting environment, site content, credentials within reach of that process, and anything else the service can touch. A public PoC, if functional, lowers the skill barrier for anyone who already has a staff login or can obtain one.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

What to do

Inferred

Until a patch is confirmed, the practical play is to shrink the attack surface the report describes. Audit who holds staff accounts, especially Contributor and other low-privilege logins, since the SVG path reportedly starts there. Limit Administrator accounts and consider disabling the theme translation feature, which the report says must be enabled for the second flaw to work.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Inferred

Keep an eye out for an official TryGhost advisory and update promptly when one lands. Nothing in the current evidence mentions a fix, a patched version, or a workaround endorsed by the vendor, so treating both flaws as live is the safer read for now.dbu.gsdbu.gs · rssOpen original sourceSee in source list

Confirmed and still uncertain

Observed

What is on the record: a researcher report describing two RCE flaws in Ghost CMS, a tracking ID PT-2026-106138, specific attack paths for each CVE, and a claim that a PoC exists for both, backed by a referenced GitHub repository for the first flaw.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list

Inferred

What is still open: there is no vendor confirmation, no patch, and no affected-version list in this batch. The GitHub repository contents were not reviewed, so the PoC's actual capability is unverified. And there is no evidence either way on whether anyone has exploited these flaws in the wild.github.comgithub.com · rssOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

What people are saying

Alleged

The voice behind this disclosure is ptdbugs, whose post states plainly: a PoC/exploit has been discovered for both CVE-2026-105642 and CVE-2026-105677. The account attributes the findings to its own research tracked as PT-2026-106138 and points readers to dbu.gs for the full writeup. No response from TryGhost and no independent researcher commentary appear in this batch.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Evolution

Inferred

The story has moved from description to demonstration, at least on paper. What began as a vulnerability report outlining two attack paths now includes a claim of a working PoC for both flaws, plus a public GitHub repository tied to the first CVE. That shift matters because reproducible code tends to pressure vendors toward a faster patch and draws more attention from opportunistic attackers. What has not changed: no fix is cited at any point in the trail.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list

Reach

Observed

2 independent groups, 1 updates, and 0 engagements.

Technical detail

Alleged

CVE-2026-105642, as described: a staff user, including one holding only the Contributor role, uploads a specially crafted SVG image that flows into bookmark card image processing. The malformed image triggers memory corruption, and the report says this can potentially lead to arbitrary code execution, meaning attacker-chosen code running on the server.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Alleged

CVE-2026-105677, as described: an Administrator loads malicious theme translation directories, and when the affected translation feature is enabled, arbitrary JavaScript executes. It requires admin-level access, which lowers the urgency compared to the first flaw, but it turns a trusted maintenance action into a code execution vector.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Alleged

The common endpoint, per the report: both vulnerabilities can result in command execution with the privileges of the Ghost server process. That is the process running the CMS itself, so successful exploitation inherits whatever that process can read, write, and execute on the host.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Sources and evidence

Observed

Three items back this story. First, the dbu.gs advisory page for PT-2026-106138, the primary tracking record, which arrived as a feed entry without body text. Second, a GitHub repository at fixedbyreboot/CVE-2026-105642-POC, the apparent home of the exploit code, also retrieved as a bare reference. Third, the X post by ptdugs, the only item with substantive text, carrying the full vulnerability descriptions.dbu.gsdbu.gs · rssOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Inferred

Confidence note: every substantive claim in this briefing traces to a single researcher account and its tracker entry. There is no vendor advisory, no independent code review, and no retrieved PoC source in the batch, so the technical details should be read as well-formed allegations awaiting confirmation.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Sources

  1. ptdbugsx.com · ptdbugs · x
  2. dbu.gsdbu.gs · rss
  3. github.comgithub.com · rss

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click