# CVE-2023-40035: Craft CMS vulnerable to Remote Code Execution via validatePath bypass

> Authenticated attackers can achieve remote code execution in Craft CMS by bypassing path validation when admin changes are enabled.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-44wr-rmwq-3phw

## What is CVE-2023-40035?

CVE-2023-40035 is a high-severity code injection vulnerability in Craftcms Craft Cms, published on 23 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Craft is a CMS for creating custom digital experiences on the web and beyond. Bypassing the validatePath function can lead to potential remote code execution. This vulnerability can lead to malicious control of vulnerable systems and data exfiltrations. Although the vulnerability is exploitable only in the authenticated users, configuration with ALLOW_ADMIN_CHANGES=true, there is still a potential security threat (Remote Code Execution). This issue has been patched in version 4.4.15 and version 3.8.15.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

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.0.0 | 3.8.15 |
| `craftcms/cms` | Packagist | From 3.0.0 | 3.8.15 |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.4.15 |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.4.15 |

Products: Craftcms Craft Cms.

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

Upgrade craftcms/cms to a fixed version for your release line: 3.8.15 or 4.4.15.

## Is CVE-2023-40035 being exploited?

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

What it is: CVE-2023-40035 is a high-severity code injection vulnerability in Craftcms Craft Cms, published on 23 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40035 exists.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 3.0.0; fixed in 3.8.15
- craftcms/cms (Packagist): affected from 3.0.0; fixed in 3.8.15
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.4.15
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.4.15

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

## Sources

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

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