Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2026-71434: 0.41% estimated exploitation activity in the next 30 days; percentile 35.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. For assets fields, files could be stored on a public, web-accessible disk. Statamic's global upload allowlist still applied, so executable types such as .php and .html remained blocked. Patches This has been fixed in 5.74.3 and 6.24.2.

Published by the source

6 Aug 2026, 19:35 UTC

Last modified by the source

6 Aug 2026, 19:56 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qhr7-v3xp-vw9m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qhr7-v3xp-vw9m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71434

Advisory: Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types
IDs: CVE-2026-71434, GHSA-qhr7-v3xp-vw9m
Record: https://patchnext.com/advisories/cve-2026-71434 (revision 2, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: statamic/cms 6.24.2, 5.74.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist statamic/cms: affected < 5.74.3; >= 6.0.0, < 6.24.2; fixed in 6.24.2, 5.74.3

## Suggested inspection (read-only)
- Packagist statamic/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on statamic/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qhr7-v3xp-vw9m (OSV record GHSA-qhr7-v3xp-vw9m lists affected ranges: Packagist statamic/cms >=0 =6.0.0 <6.24.2 (fixed))
- Verified: https://github.com/advisories/GHSA-qhr7-v3xp-vw9m (GitHub-reviewed advisory GHSA-qhr7-v3xp-vw9m lists affected ranges: Packagist statamic/cms >=0 =6.0.0 <6.24.2)

Commands are suggestions: review each one before running it.