dbcve.org
CaptchaDrupal extension · Arnabdotorg

CVE-2026-3214

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 2.0.10 / 8.x-1.17 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Drupal CAPTCHA module versions prior to 1.17.0 and 2.0.10 contain an authentication bypass vulnerability (CWE-288) where attackers can bypass CAPTCHA validation through an alternate path or channel, allowing automated attacks, spam, or unauthorized form submissions without solving CAPTCHAs.

MitigationUpgrade the Drupal CAPTCHA module to version 1.17.0 or 2.0.10 or later to resolve the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CaptchaDrupal extension
Affected:< 8.x-1.17>= 2.0.0, < 2.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Drupal CAPTCHA module is installed
    Run 'drush pm-list' or check the Drupal modules directory for the 'captcha' module folder. On the Drupal admin interface, navigate to Extend to see installed modules.
    Affected if The CAPTCHA module is present in the Drupal installation
  2. Determine the installed CAPTCHA module version
    Run 'drush pm:info captcha' or check the captcha.info.yml file in the CAPTCHA module directory for the 'version' field.
    Affected if The version is less than 8.x-1.17 or is between 2.0.0 and 2.0.9 inclusive
  3. Verify if CAPTCHA enforcement is active on forms
    Navigate to Configuration > CAPTCHA settings (admin/config/people/captcha) or check the captcha.settings.yml configuration file to see which form types have CAPTCHA enabled.
    Affected if CAPTCHA is enabled on any form types (user registration, comment forms, contact forms, etc.) and the module version falls within the affected ranges
  4. Check for suspicious form submissions without valid CAPTCHA tokens
    Review web server access logs and application logs for form submission endpoints (user/register, comment/reply, contact/*) looking for submissions that bypass expected CAPTCHA validation.
    Affected if Evidence of form submissions succeeding where the CAPTCHA validation should have been required, combined with an affected module version

The environment is affected if the Drupal CAPTCHA module is installed with a version less than 8.x-1.17 or between 2.0.0 and 2.0.9 inclusive, and CAPTCHA is actively enforced on any forms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.10 / 8.x-1.17 or later
Fixed in 2.0.108.x-1.17
Interim mitigation

Upgrade the Drupal CAPTCHA module to version 1.17.0 or 2.0.10 or later to resolve the vulnerability.

Recommended fix High confidence

Captcha 8.x-1.17 or later / 2.0.10 or later

  1. 1. Identify the exact version of the Captcha module currently installed in your Drupal site
  2. 2. For Drupal 8.x users: Upgrade to Captcha module version 8.x-1.17 or later
  3. 3. For Drupal 10.x users (2.x branch): Upgrade to Captcha module version 2.0.10 or later
  4. 4. Clear Drupal cache after upgrading: drush cr all or via admin UI at /admin/config/development/performance
  5. 5. Verify the upgrade by confirming the module version at /admin/modules
  6. 6. Test CAPTCHA functionality on forms to ensure proper operation
Caveat Standard minor version upgrade; review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Captcha Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3214 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data