# CVE-2023-48701: Statamic CMS vulnerable to Cross-site Scripting via uploaded assets

> Attackers can upload malicious HTML files disguised as images via front-end forms, leading to cross-site scripting attacks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/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:** 21 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8jjh-j3c2-cjcv

## What is CVE-2023-48701?

CVE-2023-48701 is a high-severity cross-site scripting vulnerability in statamic cms, published on 21 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

Statamic CMS is a Laravel and Git powered content management system (CMS). Prior to versions 3.4.15 an 4.36.0, HTML files crafted to look like images may be uploaded regardless of mime validation. This is only applicable on front-end forms using the "Forms" feature containing an assets field, or within the control panel which requires authentication. This issue has been patched on 3.4.15 and 4.36.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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.15 |
| `statamic/cms` | Packagist | All versions | 3.4.15 |
| `statamic/cms` | Packagist | From 4.0.0 | 4.36.0 |
| `statamic/cms` | Packagist | From 4.0.0 | 4.36.0 |

Products: Statamic Statamic.

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

Upgrade statamic/cms to a fixed version for your release line: 3.4.15 or 4.36.0.

## Is CVE-2023-48701 being exploited?

There is no known exploitation of CVE-2023-48701 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-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-48701 and fix it if it is affected.

What it is: CVE-2023-48701 is a high-severity cross-site scripting vulnerability in statamic cms, published on 21 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-48701 in the wild and no public exploit code.

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

## Sources

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

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