Skip to main content
CVE-2025-8093VulnerabilityPublished Updated

CVE-2025-8093: Drupal Authenticator Login · Authentication Bypass Using an Alternate Path or Channel

Affects Drupal Authenticator LoginSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Drupal Authenticator LoginAffected
  • =0.0.0
Fixed in–

AI-suggested

1. Upgrade the Drupal Authenticator Login module to version 2.1.8 or later as soon as the patch is released to address CVE-2025-8093. 2. Until a patch is available, restrict network access to authentication endpoints by implementing IP whitelisting or VPN-only access for administrative interfaces. 3. Employ multi-factor authentication (MFA) to add an additional layer of security beyond the vulnerable module. 4. Monitor authentication logs for unusual or repeated failed login attempts and signs of bypass attempts, using SIEM tools tailored to Drupal logs. 5. Conduct regular security audits and penetration testing focusing on authentication mechanisms to detect potential exploitation paths. 6. Isolate critical Drupal instances in segmented network zones to limit lateral movement in case of compromise. 7. Educate administrators and developers about the vulnerability and ensure timely application of security updates. 8. Implement Web Application Firewalls (WAF) with custom rules to detect and block suspicious authentication bypass attempts targeting the vulnerable module.

Description

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.

References

Community reviews

Loading reviews…