Unauthenticated CAPTCHA bypass via omitted required field
Published Jun 21, 2024 · Updated Mar 14, 2025
Broken access control in Integration of Friendly Captcha before 0.1.4 allows remote attackers to bypass CAPTCHA checks in TYPO3 forms. The EXT:form integration accepts submitted form data without enforcing that the configured CAPTCHA field is present before verification. The issue is reachable without authentication only when the third-party extension protects an EXT:form form, allowing automated submissions to pass its anti-bot gate.
Summary
What happened
Broken access control in Integration of Friendly Captcha before 0.1.4 allows remote attackers to bypass CAPTCHA checks in TYPO3 forms. The EXT:form integration accepts submitted form data without enforcing that the configured CAPTCHA field is present before verification. The issue is reachable without authentication only when the third-party extension protects an EXT:form form, allowing automated submissions to pass its anti-bot gate.
The record
- CVE
- CVE-2024-38873
- Published
- Jun 21, 2024
- Updated
- Mar 14, 2025
- Vendor
- Studio Mitte GmbH
- Product
- Integration of Friendly Captcha
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record 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.1.3
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.
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