Skip to main content
Menu
CVEs

CAPTCHA for Drupal information disclosure in login form validation feedback

CVE-2026-19030Published , updated

6.9MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

CAPTCHA for Drupal 7 lets unauthenticated attackers reach the login form remotely and test credentials, because validation feedback can still appear after a missing or incorrect CAPTCHA response. This lets an attacker tell invalid credentials apart from valid ones, even though CAPTCHA is enabled.

Written by a model

Original description

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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-19030 (CAPTCHA for Drupal 7 exposes login validation feedback after failed CAPTCHA), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-19030 (entry last updated 2026-11-20):
Affected:
- Drupal CAPTCHA for Drupal 7: from 7.x-1.0, through 7.x-1.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-19030 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-19030 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.herodevs.com/vulnerability-directory/cve-2026-19030
- https://d7es.tag1.com/security-advisories/captcha-moderately-critical-brute-force-protection-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-19030
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-19030"}.

Affected versions

cve.now Index

29Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

Questions about CVE-2026-19030

Is CVE-2026-19030 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-19030?

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

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.