# CVE-2026-112067: Captcha Bypass in extension "Accessible Form Captcha" (bw_captcha)


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-mf3p-7j87-6qr4

## What is CVE-2026-112067?

CVE-2026-112067 is a medium-severity vulnerability in TYPO3 Extension "Accessible Form Captcha", published on 20 Oct 2026. 

### Official description

The extension hides the correct answer to each CAPTCHA inside the image data of the CAPTCHA itself. Anyone who can request a CAPTCHA image can read the answer from it and submit it, so automated clients can pass the challenge. This applies to the default configuration, because the audio feature that causes the answer to be embedded is enabled by default. Forms that rely on the CAPTCHA as their only protection against automated submissions are exposed to abuse by bots.

Weakness: CWE-804 (Guessable CAPTCHA), CWE-656 (Reliance on Security Through Obscurity)

## Which versions are affected by CVE-2026-112067?


## How do I fix CVE-2026-112067?

No fix has been published for CVE-2026-112067 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112067 being exploited?

There is no known exploitation of CVE-2026-112067 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112067 and fix it if it is affected.

What it is: CVE-2026-112067 is a medium-severity vulnerability in TYPO3 Extension "Accessible Form Captcha", published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112067 in the wild and no public exploit code.

Affected product: TYPO3 Extension "Accessible Form Captcha". No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112067/ (Markdown: https://insights.sbomify.com/CVE-2026-112067/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112067
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112067
- OSV: https://osv.dev/vulnerability/CVE-2026-112067

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112067/
Summaries are generated and may contain mistakes; the official description above is the record.