CVE-2026-19030 json
CAPTCHA for Drupal 7 exposes login validation feedback after failed CAPTCHA
published 2h ago modified 2h ago also EUVD-2026-131897
- cvss
- 6.9
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-19030 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N |
Affected products
- Drupal CAPTCHA for Drupal 7
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
herodevs.com
/vulnerability-directory/cve-2026-19030
third-party-advisory
-
d7es.tag1.com
/security-advisories/captcha-moderately-critical-brute-force-protection-bypass
third-party-advisory
Sources
- CVE List CVE-2026-19030
- NVD CVE-2026-19030
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.