Skip to main content
Vulnerability Database/CVE-2026-84923

CVE-2026-84923: Drupal OTP Verification Auth Bypass Flaw

CVE-2026-84923 is an authentication bypass flaw in Drupal Email Verification, SMS Verification, and OTP Verification plugin that allows attackers to circumvent authentication controls. This article covers technical details, affected versions from 0.0.0 to 2.4.0, security impact, and recommended mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-84923 Overview

CVE-2026-84923 is an authentication bypass vulnerability in the Drupal Email Verification / SMS Verification / OTP Verification contributed module. The flaw is categorized under [CWE-288], Authentication Bypass Using an Alternate Path or Channel. Attackers can circumvent the verification workflow by reaching protected functionality through an unintended channel, defeating the module's identity-proofing controls.

The issue affects all releases from version 0.0.0 through 2.4.0. Sites that rely on the module to gate account registration, password recovery, or sensitive user actions behind email, SMS, or one-time password (OTP) verification are at risk of account takeover and unauthorized access.

Critical Impact

Attackers can bypass email, SMS, and OTP verification checks, enabling unauthorized authentication to Drupal accounts protected by the affected module.

Affected Products

  • Drupal Email Verification / SMS Verification / OTP Verification module versions 0.0.0 through 2.4.0
  • Drupal sites using the module to gate registration or login flows
  • Drupal sites using the module for password reset or sensitive action verification

Discovery Timeline

  • 2026-10-22 - CVE-2026-84923 published to NVD
  • 2026-10-22 - Last updated in NVD database
  • 2026 - Drupal Security Advisory SA-CONTRIB-2026-124 published

Technical Details for CVE-2026-84923

Vulnerability Analysis

The module enforces identity verification by sending a code to an email address or phone number and requiring the user to submit that code before completing authentication. Under CVE-2026-84923, an alternate request path reaches the post-verification state without validating that the code challenge was successfully completed.

Because the bypass avoids the verification channel entirely, the attacker never needs to intercept, guess, or brute-force the OTP. The authorization decision is made in a context that trusts prior state which has not actually been established.

Root Cause

The root cause is [CWE-288]: Authentication Bypass Using an Alternate Path or Channel. The module exposes more than one route to privileged functionality, and at least one of those routes does not enforce the verification check. Code paths that should share a single authorization gate instead implement enforcement inconsistently, so a request crafted against the weaker path proceeds as if verification had succeeded.

Attack Vector

An unauthenticated attacker interacts with the Drupal site over its standard web interface and submits requests to the alternate endpoint that handles post-verification logic. By skipping the OTP submission step, the attacker reaches an authenticated or verified session state tied to a target account or a freshly registered account.

No verified public exploit code is available at the time of writing. Technical specifics are documented in the Drupal Security Advisory SA-CONTRIB-2026-124.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-84923

Indicators of Compromise

  • Successful account logins or registrations without a corresponding OTP, SMS, or email verification event in module logs.
  • New or modified user accounts whose verification_status field indicates verified state despite no delivered code.
  • Access attempts targeting module routes that bypass the standard verification form submission.

Detection Strategies

  • Correlate Drupal watchdog authentication events with verification-dispatch events to identify sessions that completed login without a matching code challenge.
  • Review web server access logs for direct requests to module controller paths that are reached without the preceding verification form POST.
  • Audit the users_field_data table and module-specific verification tables for state mismatches between account creation time and verification time.

Monitoring Recommendations

  • Enable verbose logging on the Email/SMS/OTP Verification module and forward Drupal logs to a centralized SIEM for correlation.
  • Alert on new administrator or elevated-role account creations that occur outside of expected provisioning workflows.
  • Monitor for anomalous spikes in registration or password reset completions relative to the volume of OTP messages actually dispatched.

How to Mitigate CVE-2026-84923

Immediate Actions Required

  • Upgrade the Email Verification / SMS Verification / OTP Verification module to a release later than 2.4.0 that addresses CVE-2026-84923, as directed in the vendor advisory.
  • Audit recently created and recently modified accounts for signs of unauthorized verification bypass and reset credentials where abuse is suspected.
  • Temporarily restrict account self-registration and password reset flows if an immediate upgrade is not feasible.

Patch Information

Refer to the Drupal Security Advisory SA-CONTRIB-2026-124 for the fixed version and upgrade instructions. Apply the vendor-released update to all Drupal sites running the affected module and clear Drupal caches after the upgrade.

Workarounds

  • Disable the Email Verification / SMS Verification / OTP Verification module until the patched release can be deployed.
  • Enforce administrator approval for new account registrations through Drupal's built-in user.settings registration controls as a compensating control.
  • Place a web application firewall rule in front of the affected module routes to block requests that reach post-verification endpoints without a prior verification form submission.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.