# DRUPAL-CONTRIB-2021-007: This module provides a new UI experience for node editing using the Gutenberg Editor library.

> Anonymous users can delete blocks due to missing access validation in the Drupal Gutenberg editor module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2021

## What is DRUPAL-CONTRIB-2021-007?

DRUPAL-CONTRIB-2021-007 is a missing authorization vulnerability in drupal/gutenberg, published on 12 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module provides a new UI experience for node editing using the Gutenberg Editor library.

The module did not correctly validate access rules in certain situations allowing anonymous users to delete blocks.

## Which versions are affected by DRUPAL-CONTRIB-2021-007?


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

## How do I fix DRUPAL-CONTRIB-2021-007?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2021-007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2021-007 is a missing authorization vulnerability in drupal/gutenberg, published on 12 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2021-007 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2021-007

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