# CVE-2024-52292: Craft Allows Attackers to Read Arbitrary System Files

> Attackers with template write access can read arbitrary server files via Base64-encoded email exfiltration in Craft CMS.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 13 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** CLSA-2026-1786625623, GHSA-cw6g-qmjq-6w2w

## What is CVE-2024-52292?

CVE-2024-52292 is a high-severity path traversal vulnerability in Craftcms Craft Cms, published on 13 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Craft is a content management system (CMS). The dataUrl function can be exploited if an attacker has write permissions on system notification templates. This function accepts an absolute file path, reads the file's content, and converts it into a Base64-encoded string. By embedding this function within a system notification template, the attacker can exfiltrate the Base64-encoded file content through a triggered system email notification. Once the email is received, the Base64 payload can be decoded, allowing the attacker to read arbitrary files on the server. This is fixed in 5.4.9 and 4.12.8.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | From 3.5.13 | 4.12.8 |
| `craftcms/cms` | Packagist | From 3.5.13 | 4.12.8 |
| `craftcms/cms` | Packagist | From 5.0.0-alpha.1 | 5.4.9 |
| `craftcms/cms` | Packagist | From 5.0.0-alpha.1 | 5.4.9 |

Products: Craftcms Craft Cms.

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

Upgrade craftcms/cms to a fixed version for your release line: 4.12.8 or 5.4.9.

## Is CVE-2024-52292 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52292 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-52292 and fix it if it is affected.

What it is: CVE-2024-52292 is a high-severity path traversal vulnerability in Craftcms Craft Cms, published on 13 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52292 exists.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 3.5.13; fixed in 4.12.8
- craftcms/cms (Packagist): affected from 3.5.13; fixed in 4.12.8
- craftcms/cms (Packagist): affected from 5.0.0-alpha.1; fixed in 5.4.9
- craftcms/cms (Packagist): affected from 5.0.0-alpha.1; fixed in 5.4.9

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

## Sources

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

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