# DRUPAL-CONTRIB-2022-054: The Next.js module provides an inline preview for content.

> Authenticated users can access unauthorized content due to insufficient access checks in the Next.js module's JSON:API requests.

- **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:** 7 Sep 2022

## What is DRUPAL-CONTRIB-2022-054?

DRUPAL-CONTRIB-2022-054 is a missing authorization vulnerability in drupal/next, published on 7 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Next.js module provides an inline preview for content. Authenticated requests are made to Drupal to fetch JSON:API content and render them in an iframe from the decoupled Next.js site.

The current implementation doesn’t sufficiently check access for fetching data. All requests made to Drupal are authenticated using a single scope with elevated content access. Users without access to content could be exposed to unauthorized content.

## Which versions are affected by DRUPAL-CONTRIB-2022-054?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/next` | Packagist:https://packages.drupal.org/8 | All versions | 1.3.0 |

## How do I fix DRUPAL-CONTRIB-2022-054?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2022-054 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-054 is a missing authorization vulnerability in drupal/next, published on 7 Sep 2022. 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-2022-054 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2022-054

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