# CVE-2026-103287: Ghost 1.18.0 before 6.27.0 Server-Side Request Forgery via Webhook

> Staff users can exploit a webhook vulnerability in Ghost to perform Server-Side Request Forgery and access internal network resources.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-qhr2-wq77-6fjw

## What is CVE-2026-103287?

CVE-2026-103287 is a medium-severity server-side request forgery vulnerability in TryGhost Ghost, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Ghost versions 1.18.0 before 6.27.0 contain a server-side request forgery vulnerability in the webhooks feature that allows staff users to probe internal hosts. Attackers with staff privileges can craft webhook requests to access internal network resources from the Ghost server.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

Upgrade to a fixed version.

## Is CVE-2026-103287 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103287 is a medium-severity server-side request forgery vulnerability in TryGhost Ghost, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103287 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-103287/ (Markdown: https://insights.sbomify.com/CVE-2026-103287/index.md)
```

## Sources

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

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