# CVE-2024-52291: Local File System Validation Bypass Leading to File Overwrite, Sensitive File Access, and Potential Code Execution

> Authenticated administrators can bypass file system validation to overwrite files, access sensitive data, or execute code via SSTI in Craft CMS.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-jrh5-vhr9-qh7q

## What is CVE-2024-52291?

CVE-2024-52291 is a high-severity path traversal vulnerability in Craftcms Craft Cms, published on 13 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Craft is a content management system (CMS). A vulnerability in CraftCMS allows an attacker to bypass local file system validation by utilizing a double file:// scheme (e.g., file://file:////). This enables the attacker to specify sensitive folders as the file system, leading to potential file overwriting through malicious uploads, unauthorized access to sensitive files, and, under certain conditions, remote code execution (RCE) via Server-Side Template Injection (SSTI) payloads. Note that this will only work if you have an authenticated administrator account with allowAdminChanges enabled. This is fixed in 5.4.6 and 4.12.5.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.12.5 |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.12.5 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.4.6 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.4.6 |

Products: Craftcms Craft Cms.

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

Upgrade craftcms/cms to a fixed version for your release line: 4.12.5 or 5.4.6.

## Is CVE-2024-52291 being exploited?

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

## Other vulnerabilities in Craftcms Craft Cms

- [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild)
- [CVE-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, exploited in the wild)
- [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild)
- [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild)
- [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52291 and fix it if it is affected.

What it is: CVE-2024-52291 is a high-severity path traversal vulnerability in Craftcms Craft Cms, published on 13 Nov 2024. An attacker needs administrator access to exploit it, 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-52291 exists.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.12.5
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.12.5
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.4.6
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.4.6

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

## Sources

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

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