# CVE-2026-104413: Ghost 5.94.0 before 6.64.0 Stored XSS via Bookmark Card Images

> Staff users can inject arbitrary HTML via bookmark card images, potentially compromising other staff users' admin sessions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-5pj5-x6hq-mvq7, MINI-24jq-5r3j-pq9j

## What is CVE-2026-104413?

CVE-2026-104413 is a high-severity cross-site scripting vulnerability in TryGhost Ghost, published on 2 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Ghost from 5.94.0 before 6.64.0 contains a stored cross-site scripting vulnerability that allows staff users, including Contributors, to host arbitrary HTML by abusing bookmark card image fetching. Attackers can create bookmark cards that store non-image files from external websites as icons or thumbnails to compromise other staff users' admin sessions.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-104413?


## How do I fix CVE-2026-104413?

Upgrade to a fixed version.

## Is CVE-2026-104413 being exploited?

There is no known exploitation of CVE-2026-104413 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104413 and fix it if it is affected.

What it is: CVE-2026-104413 is a high-severity cross-site scripting vulnerability in TryGhost Ghost, published on 2 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104413 in the wild and no public exploit code.

Affected product: TryGhost Ghost. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104413/ (Markdown: https://insights.sbomify.com/CVE-2026-104413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104413
- OSV: https://osv.dev/vulnerability/CVE-2026-104413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104413/
Summaries are generated and may contain mistakes; the official description above is the record.