# GHSA-7f4f-p7mq-p4fv: Drupal External URL injection through URL aliases leading to Open Redirect

> Privileged users can create URL aliases that trigger open redirects to malicious sites, potentially facilitating phishing attacks against site visitors.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-7f4f-p7mq-p4fv?

GHSA-7f4f-p7mq-p4fv is a vulnerability in drupal/core, published on 15 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The path module in Drupal allows users with the 'administer paths' to create pretty URLs for content.
In certain circumstances the user can enter a particular path that triggers an open redirect to a malicious url.

## Which versions are affected by GHSA-7f4f-p7mq-p4fv?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 7.0 | 7.60 |
| `drupal/core` | Packagist | From 7.0 | 7.60 |
| `drupal/core` | Packagist | From 8.0.0 | 8.5.8 |
| `drupal/core` | Packagist | From 8.0.0 | 8.5.8 |
| `drupal/core` | Packagist | From 8.6.0 | 8.6.2 |
| `drupal/core` | Packagist | From 8.6.0 | 8.6.2 |

## How do I fix GHSA-7f4f-p7mq-p4fv?

Upgrade drupal/core to a fixed version for your release line: 7.60, 8.5.8 or 8.6.2.

## Is GHSA-7f4f-p7mq-p4fv being exploited?

There is no known exploitation of GHSA-7f4f-p7mq-p4fv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7f4f-p7mq-p4fv and fix it if it is affected.

What it is: GHSA-7f4f-p7mq-p4fv is a vulnerability in drupal/core, published on 15 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-7f4f-p7mq-p4fv in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 7.0; fixed in 7.60
- drupal/core (Packagist): affected from 7.0; fixed in 7.60
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.5.8
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.5.8
- drupal/core (Packagist): affected from 8.6.0; fixed in 8.6.2
- drupal/core (Packagist): affected from 8.6.0; fixed in 8.6.2

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-7f4f-p7mq-p4fv/ (Markdown: https://insights.sbomify.com/GHSA-7f4f-p7mq-p4fv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7f4f-p7mq-p4fv

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