# DRUPAL-CONTRIB-2018-040: This module enables you to delete any types of entities in bulk.

> An attacker can trick authenticated users into deleting entities via CSRF or bypass access controls to delete content without proper permissions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Jun 2018

## What is DRUPAL-CONTRIB-2018-040?

DRUPAL-CONTRIB-2018-040 is a vulnerability in drupal/entity_delete, published on 6 Jun 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

This module enables you to delete any types of entities in bulk.

The module doesn't sufficiently verify access permissions under its use cases, leading to access bypass. The module also does not protect against Cross Site Request Forgeries on its delete process.

The access bypass vulnerability is mitigated by the fact that an attacker must have a role with the permission "access content". There is no additional mitigation for the Cross Site Request Forgery vulnerability.

## Which versions are affected by DRUPAL-CONTRIB-2018-040?


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

## How do I fix DRUPAL-CONTRIB-2018-040?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2018-040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2018-040 is a vulnerability in drupal/entity_delete, published on 6 Jun 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2018-040 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2018-040

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