CVE-2026-126730: Composer/drupal/auth_login_plus vulnerability

Published Nov 11, 2026
·
Updated

This module enables you to require a second authentication factor (a time-based one-time password from an authenticator app) when users log in.

The module does not enforce the second authentication factor correctly. As a result, an attacker who has only the first factor for an account with 2FA (for example, a valid one-time login link) could trigger actions that should only follow a fully authenticated login. These include updating the account's last login time, (which also invalidates other one-time login links) and running other modules' login hooks.

The vulnerability is mitigated by the fact that the attacker must already have the account's first factor (a valid one-time login link, or a login through another module), and the impact depends on which other modules react to user logins.

Affected Software

1 affected componentFixes available
composer/drupal/auth_login_plus<1.0.3
1.0.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/drupal/auth_login_plus to a version that resolves this vulnerability.

    Fixed in 1.0.3

Event History

Nov 11, 2026
Advisory Published
via OSV·05:44 PM
Data Sourced
via OSV·05:44 PM
DescriptionAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Accounts protected by this module's second authentication factor are exposed if an attacker already possesses that account's first factor, such as a valid one-time login link or access through another login module. The practical impact also depends on which installed modules perform actions in response to user login events.

2

What does an attacker need to exploit it?

The attacker must have the target account's first authentication factor. The data specifically identifies a valid one-time login link or a login through another module as possible ways to satisfy that requirement; the attacker does not need to complete the time-based one-time-password factor.

3

What can happen if exploitation succeeds?

The attacker can trigger actions intended to occur only after a fully authenticated login. This includes updating the account's last-login time, which invalidates other one-time login links, and causing other modules' login hooks to run.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203