Automated-submission bypass via reusable security tokens
Published Mar 25, 2026 · Updated Mar 25, 2026
Authentication bypass in Drupal CAPTCHA before 1.17.0 and 2.0.0 through 2.0.9 allows remote attackers to reuse solved challenges. The module fails to invalidate used security tokens in certain submission flows, so a harvested valid token remains accepted for later form submissions. An attacker must first solve one challenge manually; replay then bypasses the anti-automation check and permits submissions that the CAPTCHA should block.
Summary
What happened
Authentication bypass in Drupal CAPTCHA before 1.17.0 and 2.0.0 through 2.0.9 allows remote attackers to reuse solved challenges. The module fails to invalidate used security tokens in certain submission flows, so a harvested valid token remains accepted for later form submissions. An attacker must first solve one challenge manually; replay then bypasses the anti-automation check and permits submissions that the CAPTCHA should block.
The record
- CVE
- CVE-2026-3214
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- Avatar Uploader Project
- Product
- CAPTCHA
- Classifications
- CWE-288
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <1.17.0
- Affected versionversion=2.0.0 <2.0.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo