- Package
- drupal/auth_login_plus
- Fixed in
- 1.0.1
- Published
- Wed 7 Oct 2026, 17:21 LisbonUpdated Mon 26 Oct 2026, 04:25 Lisbon
In plain words
An attacker with a valid Drupal core one-time login link for a victim's account can log in without completing the module's TOTP second factor. The flaw does not let an attacker log in without that valid link.
Am I affected?
Look for drupal/auth_login_plus and its version in composer.lock. The advisory lists 1.0.1 as fixed but gives no affected version range. Check whether users can log in using Drupal core's one-time login links, as that is the login route where the second factor is not enforced.
What to do
Check which version you have, then update to a fixed release for your branch (1.0.1):
composer show drupal/auth_login_plus | grep versions
composer update drupal/auth_login_plus
If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.
If you cannot update yet
The advisory identifies a limiting condition: an attacker must have access to a valid one-time login link for the victim's account.
The advisory's description
This module provides TOTP-based two-factor authentication (2FA) for Drupal.
The module doesn't enforce the second factor when a user logs in with Drupal core's one-time login link.
This vulnerability is mitigated by the fact that an attacker must have access to a valid one-time login link for a victim's account.
The advisory
- OSV.dev: DRUPAL-CONTRIB-2026-197
- The week's digest, with the other advisories from 5 Oct 2026
- All advisories for drupal/auth_login_plus