# DRUPAL-CORE-2023-001: The Media Library module does not properly check entity access in some circumstances.

> Authenticated users with content editing permissions can view unauthorized media metadata due to missing access checks in the Media Library module.

- **Severity:** Not scored
- **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:** 18 Jan 2023

## What is DRUPAL-CORE-2023-001?

DRUPAL-CORE-2023-001 is a missing authorization vulnerability in drupal/core, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Media Library module does not properly check entity access in some circumstances. This may result in users with access to edit content seeing metadata about media items they are not authorized to access.

The vulnerability is mitigated by the fact that the inaccessible media will only be visible to users who can already edit content that includes a media reference field.

This advisory is not covered by [Drupal Steward](/steward).

## Which versions are affected by DRUPAL-CORE-2023-001?

1 open source package ship an affected version, including drupal/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 8.0.0 | 9.4.10, 9.5.2, 10.0.2 |

## How do I fix DRUPAL-CORE-2023-001?

Upgrade drupal/core to a fixed version for your release line: 9.4.10, 9.5.2 or 10.0.2.

## Is DRUPAL-CORE-2023-001 being exploited?

There is no known exploitation of DRUPAL-CORE-2023-001 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CORE-2023-001 and fix it if it is affected.

What it is: DRUPAL-CORE-2023-001 is a missing authorization vulnerability in drupal/core, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CORE-2023-001 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 8.0.0; fixed in 9.4.10, 9.5.2, 10.0.2

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CORE-2023-001

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