# GHSA-7gwj-7fhm-vw4w: Drupal core unrestricted file upload

> Authenticated users with upload permissions can bypass security protections by uploading files with leading or trailing dots, such as .htaccess files.

- **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:** 15 May 2024

## What is GHSA-7gwj-7fhm-vw4w?

GHSA-7gwj-7fhm-vw4w is a vulnerability in drupal/core, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Drupal 8 core's file_save_upload() function does not strip the leading and trailing dot ('.') from filenames, like Drupal 7 did.

Users with the ability to upload files with any extension in conjunction with contributed modules may be able to use this to upload system files such as .htaccess in order to bypass protections afforded by Drupal's default .htaccess file.

After this fix, file_save_upload() now trims leading and trailing dots from filenames.

## Which versions are affected by GHSA-7gwj-7fhm-vw4w?

4 open source packages ship an affected version, including drupal/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 8.0.0 | 8.7.11 |
| `drupal/core` | Packagist | From 8.0.0 | 8.7.11 |
| `drupal/core` | Packagist | From 8.8.0 | 8.8.1 |
| `drupal/core` | Packagist | From 8.8.0 | 8.8.1 |

## How do I fix GHSA-7gwj-7fhm-vw4w?

Upgrade drupal/core to a fixed version for your release line: 8.7.11 or 8.8.1.

## Is GHSA-7gwj-7fhm-vw4w being exploited?

There is no known exploitation of GHSA-7gwj-7fhm-vw4w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7gwj-7fhm-vw4w and fix it if it is affected.

What it is: GHSA-7gwj-7fhm-vw4w is a vulnerability in drupal/core, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-7gwj-7fhm-vw4w in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.7.11
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.7.11
- drupal/core (Packagist): affected from 8.8.0; fixed in 8.8.1
- drupal/core (Packagist): affected from 8.8.0; fixed in 8.8.1

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/GHSA-7gwj-7fhm-vw4w/ (Markdown: https://insights.sbomify.com/GHSA-7gwj-7fhm-vw4w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7gwj-7fhm-vw4w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-7gwj-7fhm-vw4w/
Summaries are generated and may contain mistakes; the official description above is the record.