# DRUPAL-CONTRIB-2023-050: This module lets you craft and expose a GraphQL schema for Drupal 9 and 10.

> An attacker with low privileges can bypass access controls to read entity labels if the GraphQL schema uses specific data producers.

- **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:** 8 Nov 2023

## What is DRUPAL-CONTRIB-2023-050?

DRUPAL-CONTRIB-2023-050 is a missing authorization vulnerability in drupal/graphql, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module lets you craft and expose a GraphQL schema for Drupal 9 and 10.

The module currently does not adequately verify whether a given user has the necessary permissions to access an entity's label creating an access bypass vulnerability.

This vulnerability is mitigated by the fact that entity view and entity label access are usually handled by the same access check; developers have to opt-in for supporting different logic on entity types. Additionally your schema must make use of the EntityLabel DataProducer to be affected.

## Which versions are affected by DRUPAL-CONTRIB-2023-050?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/graphql` | Packagist:https://packages.drupal.org/8 | All versions | 3.4.0, 4.6.0 |

## How do I fix DRUPAL-CONTRIB-2023-050?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2023-050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2023-050 is a missing authorization vulnerability in drupal/graphql, published on 8 Nov 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-CONTRIB-2023-050 in the wild and no public exploit code.

Affected product: drupal/graphql. 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/DRUPAL-CONTRIB-2023-050/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-050/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2023-050

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