Unauthenticated CAPTCHA bypass via forged verification cookie
Published Sep 2, 2026 · Updated Sep 2, 2026
Cookie forgery in Drupal CAPTCHA Protected Page before 1.0.2 allows remote attackers to bypass CAPTCHA checks on protected pages. The module accepts a forged CAPTCHA verification cookie because its cookie-validation logic does not sufficiently verify that the value was legitimately issued. The affected path is reachable without authentication when the module protects a page or export, and exploitation permits access without CAPTCHA completion.
Summary
What happened
Cookie forgery in Drupal CAPTCHA Protected Page before 1.0.2 allows remote attackers to bypass CAPTCHA checks on protected pages. The module accepts a forged CAPTCHA verification cookie because its cookie-validation logic does not sufficiently verify that the value was legitimately issued. The affected path is reachable without authentication when the module protects a page or export, and exploitation permits access without CAPTCHA completion.
The record
- CVE
- CVE-2026-81168
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Vendor
- OAuth.js
- Product
- CAPTCHA Protected Page
- Classifications
- CWE-288, CAPEC-554, T1606.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 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.0.2
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