Authenticator Login
CVE-2025-8093
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid first-factor credentials
-
DeliveryReach module login endpoint over network
-
ExploitInvoke alternate authentication path to skip 2FA
-
ExecutionComplete authenticated session as victim
-
ImpactTake over account and access/modify data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
|
| Exploitation Conditions | Requires that the target Drupal site has the Authenticator Login module installed and enabled at a version below 2.1.8 to provide second-factor authentication. Exploitation also requires the attacker to possess valid primary (first-factor) credentials for a target account, since PR:L indicates low-level privileges are needed; the flaw lets that actor bypass the module's second factor via an alternate path/channel (CWE-288). Limiting factors: sites not using this specific contrib module are unaffected, no user interaction is required (UI:N), and impact is bounded to accounts whose first-factor credentials the attacker can supply. |
| Impact | Signals are moderately consistent but point to a mid-tier operational priority rather than an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring some existing privileges (PR:L), with high confidentiality, integrity, and availability impact (C:H/I:H/A:H) and unchanged scope - consistent with an authenticated attacker bypassing the module's second authentication factor to fully take over a Drupal account. Counterbalancing this, EPSS is low at 0.35% (26th percentile), there is NO CISA KEV listing and NO public exploit identified at time of analysis, so there is no evidence of active or imminent mass exploitation. The low EPSS alongside a vendor patch and no POC suggests this is a 'patch in normal cycle' item, not a drop-everything issue - though note the CVSS 8.8 HIGH score reflects worst-case account-takeover impact, which materializes only where the Authenticator Login module is actually deployed and where the attacker already holds valid first-factor credentials. A limitation: the description is terse ('allows Authentication Bypass') and does not specify the exact bypass path, so the precise PR requirement is inferred from the published CVSS vector rather than confirmed technical detail. |
| Exploit ScenarioDerived | An attacker who already possesses or has phished a user's primary Drupal credentials (username/password) leverages an alternate authentication path in the Authenticator Login module to skip the required second factor, completing login without the TOTP/one-time code and gaining full account access. No public exploit code was identified at time of analysis, and the low complexity (AC:L) means no special timing or race conditions are needed once valid first-factor credentials are held. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Second-factor authentication bypass in the Drupal Authenticator Login contrib module (versions before 2.1.8) allows an attacker who already possesses valid primary credentials for a target account to reach authenticated access without completing the module's two-factor challenge. The issue is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so it is remotely reachable with low privileges and no user interaction, but impact is bounded to accounts whose first-factor credentials the attacker can already supply, and only sites with this specific contrib module installed and enabled are exposed. No public exploit code has been identified at time of analysis, EPSS is low at 0.35% (26th percentile), and the vendor has released a fix, making this a mid-tier operational priority rather than an emergency.
RemediationAI
Apply the vendor fix: Drupal security advisory SA-CONTRIB-2025-098 (https://www.drupal.org/sa-contrib-2025-098) documents a vendor-released patch - upgrade the Authenticator Login contrib module to version 2.1.8 or later using Composer (composer update drupal/authenticator_login) and run the Drupal database updates. Because exploitation depends on the attacker first holding valid primary credentials for a target account (PR:L), reinforcing the first factor materially reduces exposure while patching is scheduled: enforce strong, unique passwords for all accounts with access to the site, and prioritize patching for any account with elevated Drupal roles. Where the upgrade cannot be applied immediately, the module can be disabled or uninstalled, but note the trade-off - doing so removes the second factor for every account, so only take this step if an equivalent MFA control (for example, an alternative 2FA module or an SSO/IdP-enforced second factor) is already in place. Additionally, audit recent authentication and session logs for successful logins that never completed a second-factor challenge, and invalidate or rotate sessions and credentials for any accounts that cannot be accounted for. There is no indication of active exploitation and no public exploit code identified at time of analysis, so patching on a normal maintenance cycle is appropriate.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in composer
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Drupal's Authenticator Login is a contributed module that adds a second authentication factor to the site's login flow, and CVE-2025-8093 is classified as CWE-288: Authentication Bypass Using an Alternate Path or Channel. That CWE class describes a situation where the application enforces an authentication control on one expected entry point but leaves a functionally equivalent route or channel that reaches the same protected state without that control. Here the module's second-factor gate is not applied uniformly across every path that can establish an authenticated Drupal session, so an actor who can supply valid first-factor credentials can traverse an alternative path and land in an authenticated session while skipping the module's 2FA step entirely. The affected CPE (cpe:2.3:a:authenticator_login_project:authenticator_login:*:*:*:*:*:drupal:*:*) confirms the vulnerable package is the Drupal contrib module itself, not Drupal core, and the affected range spans every release from 0.0.0 up to, but excluding, 2.1.8. The vector's PR:L reflects that the attacker must already hold low-privilege, authenticated context (i.e., working primary credentials); the flaw is in the step-up to the second factor, not in the initial credential check. No server-side memory corruption, injection, or remote code execution primitive is involved - this is purely a control-flow gap in the authentication pipeline.
Know when Authenticator Login gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network login endpoint (AV:N), no special conditions (AC:L); bypass still presupposes valid first-factor credentials so PR:L, and full account takeover yields C/I/A:H.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
DescriptionCVE.org
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Authenticator Login allows Authentication Bypass.This issue affects Authenticator Login: from 0.0.0 before 2.1.8.
Executive ViewAI
The Drupal Authenticator Login contrib module, used to enforce two-factor authentication on Drupal sites, contains a high-severity bypass that allows an authenticated attacker with valid primary credentials to skip the second-factor challenge and gain full account access. This affects only organizations running this specific module, and the primary risk is to accounts whose passwords may already be compromised or reused. Leadership should prioritize remediation because it directly undermines a key access control, though no public exploit identified at time of analysis and the vendor has released a patch.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
More in Authenticator Login
View allMissing Authorization vulnerability in Drupal Authenticator Login allows Forceful Browsing.0.0 before 2.0.6. Rated criti
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Authenticator Login allows Authenticati
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB