# CVE-2023-31133: Ghost vulnerable to disclosure of private API fields

> Attackers can reveal private API fields via brute force on public endpoints, exposing sensitive data in Ghost CMS installations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** BIT-ghost-2023-31133, GHSA-r97q-ghch-82j9

## What is CVE-2023-31133?

CVE-2023-31133 is a high-severity vulnerability in TryGhost Ghost, published on 8 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ghost is an app for new-media creators with tools to build a website, publish content, send newsletters, and offer paid subscriptions to members. Prior to version 5.46.1, due to a lack of validation when filtering on the public API endpoints, it is possible to reveal private fields via a brute force attack.

Ghost(Pro) has already been patched. Maintainers can find no evidence that the issue was exploited on Ghost(Pro) prior to the patch being added. Self-hosters are impacted if running Ghost a version below v5.46.1. v5.46.1 contains a fix for this issue. As a workaround, add a block for requests to `/ghost/api/content/*` where the `filter` query parameter contains `password` or `email`.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-31133?

3 open source packages ship an affected version, including ghost. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ghost` | Bitnami | All versions | 5.46.1 |
| `ghost` | npm | All versions | 5.46.1 |
| `ghost` | npm | All versions | 5.46.1 |

Products: Ghost Ghost.

## How do I fix CVE-2023-31133?

Upgrade ghost to 5.46.1 or later.

## Is CVE-2023-31133 being exploited?

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

## Other vulnerabilities in TryGhost Ghost

- [CVE-2022-27139](https://insights.sbomify.com/CVE-2022-27139/): Arbitrary file upload in Ghost (critical 9.8)
- [CVE-2022-28397](https://insights.sbomify.com/CVE-2022-28397/): Arbitrary file upload in Ghost (critical 9.8)
- [CVE-2022-41654](https://insights.sbomify.com/CVE-2022-41654/): ghost vulnerable to unauthorized newsletter modification via improper access controls (critical 9.6)
- [CVE-2026-26980](https://insights.sbomify.com/CVE-2026-26980/): Ghost has a SQL Injection in its Content API (critical 9.4)
- [CVE-2024-34451](https://insights.sbomify.com/CVE-2024-34451/): Security feature bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31133 and fix it if it is affected.

What it is: CVE-2023-31133 is a high-severity vulnerability in TryGhost Ghost, published on 8 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31133 in the wild and no public exploit code.

Affected packages and fixed versions:
- ghost (Bitnami): affected all versions; fixed in 5.46.1
- ghost (npm): affected all versions; fixed in 5.46.1
- ghost (npm): affected all versions; fixed in 5.46.1

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-2023-31133/ (Markdown: https://insights.sbomify.com/CVE-2023-31133/index.md)
```

## Sources

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

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