# CVE-2018-3814: Craft CMS PHP Code Injection Vulnerability

> Remote attackers can execute arbitrary PHP code by uploading a malicious file disguised as an image and renaming it via the asset replacement feature.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r342-vjc4-wrmj

## What is CVE-2018-3814?

CVE-2018-3814 is a high-severity vulnerability in Craftcms Craft Cms, published on 1 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Craft CMS 2.6.3000 allows remote attackers to execute arbitrary PHP code by using the "Assets->Upload files" screen and then the "Replace it" option, because this allows a .jpg file to have embedded PHP code, and then be renamed to a .php extension.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2018-3814?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | All versions to 2.6.3000 | None |
| `craftcms/cms` | Packagist | All versions to 2.6.3000 | None |

Products: Craftcms Craft Cms.

## How do I fix CVE-2018-3814?

No fix has been published for CVE-2018-3814 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-3814 being exploited?

There is no known exploitation of CVE-2018-3814 in the wild and no public exploit code.

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

What it is: CVE-2018-3814 is a high-severity vulnerability in Craftcms Craft Cms, published on 1 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3814 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected all versions up to 2.6.3000; no fix listed
- craftcms/cms (Packagist): affected all versions up to 2.6.3000; no fix listed

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

## Sources

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

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