VulnerabilityPublished 25 Mar 2026

CVE-2026-1917: Drupal Login Disable · Authentication Bypass Using an Alternate Path or Channel

Affects Drupal Login DisableSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.1.3 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.1.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Drupal Login Disable to 2.1.3.

Affected software

Product	Affected	Fixed in
DrupalLogin Disable	Affected <2.1.3	Fixed in 2.1.3

AI-suggested

Immediately upgrade the Drupal Login Disable module to version 2.1.3 or later once it becomes available to ensure the vulnerability is patched.
In the interim, disable the Login Disable module if feasible, especially on high-value or publicly accessible sites, to prevent exploitation.
Implement additional access control measures at the web server or application firewall level to restrict access to login pages or administrative interfaces.
Monitor Drupal site logs for unusual login attempts or access patterns that may indicate exploitation attempts.
Employ multi-factor authentication (MFA) on Drupal administrative accounts to reduce the impact of potential unauthorized access.
Conduct regular security audits and vulnerability scans focused on Drupal modules and configurations.
Stay informed through official Drupal security advisories and community channels for updates and patches related to this vulnerability.
Consider deploying web application firewalls (WAFs) with custom rules to detect and block attempts to exploit alternate authentication paths.

Description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Login Disable allows Functionality Bypass.This issue affects Login Disable: from 0.0.0 before 2.1.3.

Impact

The primary impact of CVE-2026-1917 is unauthorized access to Drupal websites that use the vulnerable Login Disable module. Attackers exploiting this vulnerability can bypass authentication controls, potentially gaining access to restricted areas or administrative functions. This can lead to data breaches, unauthorized content modification, privilege escalation, and disruption of website operations. The compromise of Drupal sites can also serve as a foothold for further attacks within an organization's network, including lateral movement and data exfiltration. Given Drupal's widespread use in government, education, and enterprise sectors, the vulnerability could affect a broad range of organizations globally. The lack of authentication requirement and ease of exploitation increase the risk of automated attacks and mass exploitation campaigns once exploit code becomes available. The vulnerability undermines the integrity and confidentiality of affected systems and could also impact availability if attackers modify or disable critical site functions.

CWE-288Authentication Bypass Using an Alternate Path or Channel (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
Architecture and Design
Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Directory Indexing (opens in a new tab)
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-contrib-2026-008 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Mar 2026, 16:04 UTC

WeaknessesCWE-288

Technical details

References

Community reviews

Related threats