# CVE-2024-38873: FriendlyCaptcha Plugin for TYPO3 Captcha Check Bypass

> Remote attackers can bypass CAPTCHA verification in TYPO3 form submissions by omitting the required field, enabling automated spam or abuse.

- **Severity:** Medium 5.3 (`CVSS:3.1/AC:L/AV:N/A:L/C:N/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jun 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-jg62-h7pv-hxgv

## What is CVE-2024-38873?

CVE-2024-38873 is a medium-severity vulnerability in n/a, published on 21 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the friendlycaptcha_official (aka Integration of Friendly Captcha) extension before 0.1.4 for TYPO3. The extension fails to check the requirement of the captcha field in submitted form data, allowing a remote user to bypass the captcha check. This only affects the captcha integration for the ext:form extension.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-38873?

2 open source packages ship an affected version, including studiomitte/friendlycaptcha.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `studiomitte/friendlycaptcha` | Packagist | All versions | 0.1.4 |
| `studiomitte/friendlycaptcha` | Packagist | All versions | 0.1.4 |

## How do I fix CVE-2024-38873?

Upgrade studiomitte/friendlycaptcha to 0.1.4 or later.

## Is CVE-2024-38873 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38873 and fix it if it is affected.

What it is: CVE-2024-38873 is a medium-severity vulnerability in n/a, published on 21 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38873 in the wild and no public exploit code.

Affected packages and fixed versions:
- studiomitte/friendlycaptcha (Packagist): affected all versions; fixed in 0.1.4
- studiomitte/friendlycaptcha (Packagist): affected all versions; fixed in 0.1.4

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-2024-38873/ (Markdown: https://insights.sbomify.com/CVE-2024-38873/index.md)
```

## Sources

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

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