# CVE-2023-47129: Statamic CMS remote code execution via front-end form uploads

> Attackers can upload malicious PHP files disguised as images via front-end forms to execute arbitrary code on Statamic CMS installations.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Nov 2023
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-72hg-5wr5-rmfc

## What is CVE-2023-47129?

CVE-2023-47129 is a high-severity vulnerability in statamic cms, published on 10 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Statmic is a core Laravel content management system Composer package. Prior to versions 3.4.13 and 4.33.0, on front-end forms with an asset upload field, PHP files crafted to look like images may be uploaded. This only affects forms using the "Forms" feature and not just _any_ arbitrary form. This does not affect the control panel. This issue has been patched in 3.4.13 and 4.33.0.

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

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

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.13 |
| `statamic/cms` | Packagist | All versions | 3.4.13 |
| `statamic/cms` | Packagist | From 4.0.0 | 4.33.0 |
| `statamic/cms` | Packagist | From 4.0.0 | 4.33.0 |

Products: Statamic Statamic.

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

Upgrade statamic/cms to a fixed version for your release line: 3.4.13 or 4.33.0.

## Is CVE-2023-47129 being exploited?

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

Public exploit code:

- Statamic CMS versions <4.33.0 vulnerable to "Remote Code Execution"  (github_poc): https://github.com/Cyber-Wo0dy/CVE-2023-47129

## 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-2023-48217](https://insights.sbomify.com/CVE-2023-48217/): Remote code execution via form uploads in statamic/cms (high 8.8)
- [CVE-2017-11422](https://insights.sbomify.com/CVE-2017-11422/): Statamic framework Incorrect Permission Assignment (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47129 is a high-severity vulnerability in statamic cms, published on 10 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-47129 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 3.4.13
- statamic/cms (Packagist): affected all versions; fixed in 3.4.13
- statamic/cms (Packagist): affected from 4.0.0; fixed in 4.33.0
- statamic/cms (Packagist): affected from 4.0.0; fixed in 4.33.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-47129/ (Markdown: https://insights.sbomify.com/CVE-2023-47129/index.md)
```

## Sources

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

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