CVE-2026-19030 in CAPTCHAinfo

Summary

by MITRE • 11/21/2026

Observable Discrepancy vulnerability in Drupal CAPTCHA for Drupal 7 allows unauthenticated attackers to test login credentials despite CAPTCHA protection.

When CAPTCHA is enabled on Drupal login forms, normal form validation can still run after a missing or incorrect CAPTCHA response. This may expose credential validation feedback and allow an attacker to distinguish invalid credentials from valid credentials paired with a failed CAPTCHA.



This issue affects CAPTCHA for Drupal 7: from 7.x-1.0 through 7.x-1.7.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in the CAPTCHA module for Drupal version 7, specifically affecting releases from 7.x-1.0 through 7.x-1.7, represents a significant flaw in the implementation of defense-in-depth security controls. This issue is classified as an Observable Discrepancy, which falls under the broader category of CWE-203: Observable Response Discrepancy and aligns with MITRE ATT&CK technique T1110: Brute Force. The core function of a CAPTCHA challenge is to prevent automated scripts from performing credential stuffing or brute force attacks by introducing a barrier that requires human-like interaction. However, the flaw in this implementation allows unauthenticated attackers to bypass the intended security boundary and extract sensitive information about user credentials through timing analysis or response code differentiation.

The technical root cause of this vulnerability lies in the order of operations within the form validation pipeline. When CAPTCHA is enabled on Drupal login forms, the system is designed to halt further processing if the CAPTCHA challenge is not solved correctly. In a secure implementation, any failure in CAPTCHA verification should result in an immediate rejection of the request without proceeding to validate the username and password fields. However, due to this flaw, normal form validation logic continues to execute even when the CAPTCHA response is missing or incorrect. This means that while the login attempt will ultimately fail, the system proceeds far enough into the authentication process to perform credential checks against the database.

This operational behavior creates a critical side channel for attackers. By observing the server's response time or specific error messages returned after submitting invalid credentials with an invalid CAPTCHA, an attacker can distinguish between two distinct failure states: one where the username does not exist in the system and another where the username exists but the password is incorrect. In many web applications, including Drupal, there are often subtle differences in how these errors are handled or timed. For instance, a non-existent user might trigger a different database query path than an existing user with wrong credentials, leading to measurable discrepancies in response latency or HTTP status codes. This allows an attacker to enumerate valid usernames without needing to solve the CAPTCHA for each attempt effectively neutralizing the protective value of the CAPTCHA mechanism against targeted attacks.

The impact of this vulnerability is particularly severe because it facilitates credential enumeration and subsequent brute force attacks. An attacker can first identify which usernames are registered on the Drupal site by sending requests with invalid CAPTCHAs and observing which responses indicate that a user account exists. Once valid usernames are identified, the attacker can focus their efforts on those specific accounts, potentially using more sophisticated techniques or leveraging leaked password databases to guess passwords. This undermines the primary purpose of implementing CAPTCHA on login forms, which is to protect against automated credential guessing attacks. The vulnerability effectively renders the CAPTCHA protection useless for preventing information disclosure during authentication attempts.

Mitigation strategies must address both the immediate technical flaw and broader security posture. For administrators running affected versions of Drupal 7, upgrading to a patched version of the CAPTCHA module that corrects the validation order is essential. If an upgrade is not immediately feasible, implementing a web application firewall rule can help by blocking requests that exhibit patterns consistent with this enumeration attack or by enforcing stricter rate limiting on login endpoints regardless of CAPTCHA status. Additionally, ensuring that all authentication failures return generic error messages without distinguishing between invalid usernames and incorrect passwords can reduce the effectiveness of such attacks. It is also recommended to implement multi-factor authentication where possible, as this adds an additional layer of security that cannot be bypassed by simple credential enumeration. Regular monitoring for unusual login patterns and implementing account lockout policies after a certain number of failed attempts further mitigates the risk posed by this vulnerability.

Responsible

Drupal

Reservation

08/06/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00469

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!