# CVE-2023-5256: Drupal core - Critical - Cache poisoning - SA-CORE-2023-006

> Drupal core leaks sensitive error backtraces via JSON:API, allowing anonymous users to gain privileged access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2023
- **Updated:** 23 Sep 2024
- **Also known as:** BIT-drupal-2023-5256, DRUPAL-CORE-2023-006, GHSA-rjqg-3h9m-fx5x, UBUNTU-CVE-2023-5256

## What is CVE-2023-5256?

CVE-2023-5256 is a high-severity vulnerability in Drupal Drupal, published on 28 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In certain scenarios, Drupal's JSON:API module will output error backtraces. With some configurations, this may cause sensitive information to be cached and made available to anonymous users, leading to privilege escalation.

This vulnerability only affects sites with the JSON:API module enabled, and can be mitigated by uninstalling JSON:API.

The core REST and contributed GraphQL modules are not affected.

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

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

8 open source packages ship an affected version, including drupal/core and drupal. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 10.0.0 | 10.0.11 |
| `drupal/core` | Packagist | From 10.0.0 | 10.0.11 |
| `drupal/core` | Packagist | From 10.1.0 | 10.1.4 |
| `drupal/core` | Packagist | From 10.1.0 | 10.1.4 |
| `drupal/core` | Packagist | From 8.7.0 | 9.5.11, 10.0.11, 10.1.4 |
| `drupal/core` | Packagist | From 8.7.0 | 9.5.11 |
| `drupal/core` | Packagist | From 8.7.0 | 9.5.11 |
| `drupal` | Bitnami | From 8.7.0 | 9.5.11, 10.0.11, 10.1.4 |

Products: Drupal Drupal.

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

Upgrade drupal/core to a fixed version for your release line: 10.0.11, 10.1.4 or 9.5.11.

## Is CVE-2023-5256 being exploited?

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

## Other vulnerabilities in Drupal Drupal

- [CVE-2026-9082](https://insights.sbomify.com/CVE-2026-9082/): Drupal Core SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-13671](https://insights.sbomify.com/CVE-2020-13671/): Drupal core Un-restricted Upload of File (high 8.8, exploited in the wild)
- [CVE-2019-6340](https://insights.sbomify.com/CVE-2019-6340/): Drupal Core Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2009-3352](https://insights.sbomify.com/CVE-2009-3352/): Other in n/a (critical 10.0)
- [CVE-2024-55636](https://insights.sbomify.com/CVE-2024-55636/): Drupal core - Less critical - Gadget chain - SA-CORE-2024-006 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5256 is a high-severity vulnerability in Drupal Drupal, published on 28 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5256 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 10.0.0; fixed in 10.0.11
- drupal/core (Packagist): affected from 10.0.0; fixed in 10.0.11
- drupal/core (Packagist): affected from 10.1.0; fixed in 10.1.4
- drupal/core (Packagist): affected from 10.1.0; fixed in 10.1.4
- drupal/core (Packagist): affected from 8.7.0; fixed in 9.5.11, 10.0.11, 10.1.4
- drupal/core (Packagist): affected from 8.7.0; fixed in 9.5.11
- drupal/core (Packagist): affected from 8.7.0; fixed in 9.5.11
- drupal (Bitnami): affected from 8.7.0; fixed in 9.5.11, 10.0.11, 10.1.4

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

## Sources

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

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