# CVE-2024-24570: Statamic account takeover via XSS and password reset link

> Attackers can upload malicious HTML files disguised as images to execute XSS, potentially stealing password reset tokens and taking over user accounts.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **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:** 1 Feb 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-vqxq-hvxw-9mv9

## What is CVE-2024-24570?

CVE-2024-24570 is a high-severity cross-site scripting vulnerability in statamic cms, published on 1 Feb 2024. 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 is a Laravel and Git powered CMS. HTML files crafted to look like jpg files are able to be uploaded, allowing for XSS. This affects the front-end forms with asset fields without any mime type validation, asset fields in the control panel, and asset browser in the control panel. Additionally, if the XSS is crafted in a specific way, the "copy password reset link" feature may be exploited to gain access to a user's password reset token and gain access to their account. The authorized user is required to execute the XSS in order for the vulnerability to occur. In versions 4.46.0 and 3.4.17, the XSS vulnerability has been patched, and the copy password reset link functionality has been disabled.

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

## Which versions are affected by CVE-2024-24570?

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.17 |
| `statamic/cms` | Packagist | All versions | 3.4.17 |
| `statamic/cms` | Packagist | From 4.00 | 4.46.0 |
| `statamic/cms` | Packagist | From 4.00 | 4.46.0 |

Products: Statamic Statamic.

## How do I fix CVE-2024-24570?

Upgrade statamic/cms to a fixed version for your release line: 3.4.17 or 4.46.0.

## Is CVE-2024-24570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24570 exists.

## 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-2024-24570 and fix it if it is affected.

What it is: CVE-2024-24570 is a high-severity cross-site scripting vulnerability in statamic cms, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24570 exists.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 3.4.17
- statamic/cms (Packagist): affected all versions; fixed in 3.4.17
- statamic/cms (Packagist): affected from 4.00; fixed in 4.46.0
- statamic/cms (Packagist): affected from 4.00; fixed in 4.46.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-2024-24570/ (Markdown: https://insights.sbomify.com/CVE-2024-24570/index.md)
```

## Sources

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

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