# CVE-2026-71434: Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types

> Unauthenticated attackers can upload disallowed file types via public frontend forms, bypassing administrator restrictions on file uploads.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-qhr7-v3xp-vw9m

## What is CVE-2026-71434?

CVE-2026-71434 is a medium-severity vulnerability in statamic cms, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.74.3 and 6.24.2, public frontend forms did not enforce the file upload restrictions that the Control Panel enforces, so an unauthenticated visitor could upload file types an administrator had intended to disallow through a form's assets or files field, and for assets fields, files could be stored on a public, web-accessible disk, though the application's global upload allowlist still blocked executable types such as .php and .html. This issue is fixed in versions 5.74.3 and 6.24.2.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

4 open source packages ship an affected version, including statamic/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 5.74.3 |
| `statamic/cms` | Packagist | All versions | 5.74.3 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.24.2 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.24.2 |

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

Upgrade statamic/cms to a fixed version for your release line: 5.74.3 or 6.24.2.

## Is CVE-2026-71434 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71434 is a medium-severity vulnerability in statamic cms, published on 6 Aug 2026. 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-2026-71434 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 5.74.3
- statamic/cms (Packagist): affected all versions; fixed in 5.74.3
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.24.2
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.24.2

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

## Sources

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

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