# CVE-2023-48217: Remote code execution via form uploads in statamic/cms

> Attackers can upload malicious PHP files disguised as images to execute arbitrary code on Statamic CMS installations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Nov 2023
- **Updated:** 30 Aug 2024
- **Also known as:** GHSA-2r53-9295-3m86

## What is CVE-2023-48217?

CVE-2023-48217 is a high-severity vulnerability in statamic cms, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Statamic is a flat-first, Laravel + Git powered CMS designed for building websites. In affected versions certain additional PHP files crafted to look like images may be uploaded regardless of mime type validation rules. This affects front-end forms using the "Forms" feature, and asset upload fields in the control panel. Malicious users could leverage this vulnerability to upload and execute code. This issue has been patched in versions 3.4.14 and 4.34.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-48217?

4 open source packages ship an affected version, including statamic/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 3.4.14 |
| `statamic/cms` | Packagist | All versions | 3.4.14 |
| `statamic/cms` | Packagist | From 4.0.0 | 4.34.0 |
| `statamic/cms` | Packagist | From 4.0.0 | 4.34.0 |

Products: Statamic Statamic.

## How do I fix CVE-2023-48217?

Upgrade statamic/cms to a fixed version for your release line: 3.4.14 or 4.34.0.

## Is CVE-2023-48217 being exploited?

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

## Other vulnerabilities in statamic cms

- [CVE-2021-45364](https://insights.sbomify.com/CVE-2021-45364/): Code injection in n/a (critical 9.8)
- [CVE-2026-27593](https://insights.sbomify.com/CVE-2026-27593/): Statamic is vulnerable to account takeover via password reset link injection (critical 9.3)
- [CVE-2026-27939](https://insights.sbomify.com/CVE-2026-27939/): Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass (high 8.8)
- [CVE-2017-11422](https://insights.sbomify.com/CVE-2017-11422/): Statamic framework Incorrect Permission Assignment (high 8.8)
- [CVE-2026-33172](https://insights.sbomify.com/CVE-2026-33172/): Statamic has Stored XSS via SVG Sanitization Bypass (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48217 and fix it if it is affected.

What it is: CVE-2023-48217 is a high-severity vulnerability in statamic cms, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-48217 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 3.4.14
- statamic/cms (Packagist): affected all versions; fixed in 3.4.14
- statamic/cms (Packagist): affected from 4.0.0; fixed in 4.34.0
- statamic/cms (Packagist): affected from 4.0.0; fixed in 4.34.0

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

## Sources

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

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