# DRUPAL-CONTRIB-2022-001: This module enables you to login with an email address.

> Attackers with blocked accounts can bypass authentication checks to log in via email, potentially taking over accounts.

- **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:** 5 Jan 2022

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

DRUPAL-CONTRIB-2022-001 is an authentication bypass vulnerability in drupal/super_login, published on 5 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module enables you to login with an email address.

The module doesn't sufficiently check if a user account is active when using email login.

This vulnerability is mitigated by the fact that an attacker must have an account in the website that is blocked.

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


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

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-001 is an authentication bypass vulnerability in drupal/super_login, published on 5 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2022-001 in the wild and no public exploit code.

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

## Sources

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

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