VulnerabilityPublished 25 Mar 2026

CVE-2026-3214: Drupal CAPTCHA · Authentication Bypass Using an Alternate Path or Channel

Affects Drupal CAPTCHASource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.0.10 or 1.17.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 29 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 CAPTCHA to 2.0.10 or 1.17.0.

Affected software

Product	Affected	Fixed in
DrupalCAPTCHA	Affected >=2.0.0 <2.0.10	Fixed in 2.0.10
DrupalCAPTCHA	Affected <1.17.0	Fixed in 1.17.0

AI-suggested

To mitigate CVE-2026-3214, organizations should immediately upgrade the Drupal CAPTCHA module to version 1.17.0 or 2.0.10 or later, where the vulnerability has been addressed. It is critical to verify the module version across all Drupal instances and apply patches promptly. Beyond patching, organizations should implement additional controls such as: 1) Restricting access to administrative and sensitive areas of Drupal sites via IP whitelisting or VPNs to reduce exposure. 2) Employing Web Application Firewalls (WAFs) with rules to detect and block suspicious requests that attempt to bypass CAPTCHA challenges. 3) Monitoring logs for unusual access patterns or repeated failed CAPTCHA attempts that may indicate exploitation attempts. 4) Conducting regular security audits and vulnerability scans to identify outdated modules and configuration weaknesses. 5) Educating site administrators on secure module management and the importance of timely updates. These specific measures complement patching and help reduce the attack surface and detect potential exploitation attempts early.

Description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal CAPTCHA allows Functionality Bypass.This issue affects CAPTCHA: from 0.0.0 before 1.17.0, from 2.0.0 before 2.0.10.

Impact

The authentication bypass vulnerability in Drupal CAPTCHA can have significant impacts on organizations worldwide that use Drupal for web content management. By circumventing CAPTCHA verification, attackers can potentially gain unauthorized access to administrative or restricted functionalities, leading to unauthorized data access, content manipulation, or further exploitation of the web application. This can compromise the confidentiality and integrity of organizational data and web services. The bypass may also facilitate automated attacks such as spam submissions, brute force attempts, or injection of malicious content, degrading the availability and trustworthiness of affected websites. Organizations relying on Drupal for critical web infrastructure may face reputational damage, regulatory compliance issues, and operational disruptions if this vulnerability is exploited. The lack of authentication or user interaction requirements for exploitation increases the risk of automated mass attacks. Although no known exploits are currently reported, the vulnerability's presence in widely deployed Drupal CAPTCHA versions means that many organizations remain exposed until patches are applied. The impact is particularly severe for organizations with public-facing Drupal sites that rely on CAPTCHA to prevent abuse and unauthorized access.

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-015 (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:03 UTC

WeaknessesCWE-288

Technical details

References

Community reviews

Related threats