# DRUPAL-CONTRIB-2022-023: This module enables you to manage and delete files.

> Unauthenticated users can delete unmanaged files if views lack proper access control, leading to data modification.

- **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:** 9 Feb 2022

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

DRUPAL-CONTRIB-2022-023 is a missing authorization vulnerability in drupal/fancy_file_delete, published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables you to manage and delete files.

The module doesn't sufficiently protect unmanaged files from view under the scenario unauthenticated user knows path to visit the view and can attempt to delete files which results in duplicate files being created.

To mitigate this issue without deploying code, review all views that are based on Fancy File Delete and ensure they have an access control set to use the permission "administer unmanaged files entities".

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


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

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

Change a configuration setting.

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

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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