# DRUPAL-CONTRIB-2019-063: The External Link Filter module provides an input filter that replaces external links by a local link that redirects to the target URL.

> An attacker can craft malicious links that redirect users to unintended external sites, potentially facilitating phishing attacks.

- **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:** 14 Aug 2019

## What is DRUPAL-CONTRIB-2019-063?

DRUPAL-CONTRIB-2019-063 is a vulnerability in drupal/elf, published on 14 Aug 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The External Link Filter module provides an input filter that replaces external links by a local link that redirects to the target URL.

The module did not have protection for the Redirect URL to go where content authors intended.

## Which versions are affected by DRUPAL-CONTRIB-2019-063?


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

## How do I fix DRUPAL-CONTRIB-2019-063?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2019-063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-063 is a vulnerability in drupal/elf, published on 14 Aug 2019. 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-2019-063 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-063

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