# DRUPAL-CONTRIB-2020-021: This module enables you to force a password update when using password reset link.

> A Drupal module allows attackers to log in as another user via a crafted URL, leading to account takeover.

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

## What is DRUPAL-CONTRIB-2020-021?

DRUPAL-CONTRIB-2020-021 is an authentication bypass vulnerability in drupal/prlp, published on 27 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This module enables you to force a password update when using password reset link.  
The module doesn't sufficiently validate the login URL allowing a malicious user to use a specially crafted URL to log in as another user.

## Which versions are affected by DRUPAL-CONTRIB-2020-021?


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

## How do I fix DRUPAL-CONTRIB-2020-021?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2020-021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2020-021 is an authentication bypass vulnerability in drupal/prlp, published on 27 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2020-021 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2020-021

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