# CVE-2025-34086: Bolt CMS Authenticated Remote Code Execution via Profile Injection and File Rename

> Authenticated attackers can inject PHP code into user profiles and rename session files to achieve remote code execution in Bolt CMS.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jul 2025
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-p9qc-8jjx-g8cg

## What is CVE-2025-34086?

CVE-2025-34086 is a high-severity code injection vulnerability in Bolt CMS, published on 3 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Bolt CMS versions 3.7.0 and earlier contain a chain of vulnerabilities that together allow an authenticated user to achieve remote code execution. A user with valid credentials can inject arbitrary PHP code into the displayname field of the user profile, which is rendered unsanitized in backend templates. The attacker can then list and rename cached session files via the /async/browse/cache/.sessions and /async/folder/rename endpoints. By renaming a .session file to a path under the publicly accessible /files/ directory with a .php extension, the attacker can turn the injected code into an executable web shell. Finally, the attacker triggers the payload via a crafted HTTP GET request to the rogue file.

NOTE: The vendor announced that Bolt 3 reached end-of-life after 31 December 2021.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-34086?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bolt/bolt` | Packagist | All versions to 3.7.0 | None |
| `bolt/bolt` | Packagist | All versions to 3.7.0 | None |

Products: Boltcms Bolt.

## How do I fix CVE-2025-34086?

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

## Is CVE-2025-34086 being exploited?

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

Public exploit code:

- Bolt CMS 3.7.0 - Authenticated Remote Code Execution (metasploit)

## Other vulnerabilities in Bolt CMS

- [CVE-2022-31321](https://insights.sbomify.com/CVE-2022-31321/): Path traversal in n/a (critical 9.1)
- [CVE-2019-10874](https://insights.sbomify.com/CVE-2019-10874/): Bolt Cross Site Request Forgery (CSRF) (high 8.8)
- [CVE-2019-9185](https://insights.sbomify.com/CVE-2019-9185/): Bolt Unrestricted Upload of File with Dangerous Type (high 8.8)
- [CVE-2020-4040](https://insights.sbomify.com/CVE-2020-4040/): CSRF issue on preview pages in Bolt CMS (high 8.6)
- [CVE-2021-27367](https://insights.sbomify.com/CVE-2021-27367/): Path traversal in bolt/core (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34086 and fix it if it is affected.

What it is: CVE-2025-34086 is a high-severity code injection vulnerability in Bolt CMS, published on 3 Jul 2025. Any signed-in user can exploit it over the network, 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-2025-34086 exists.

Affected packages and fixed versions:
- bolt/bolt (Packagist): affected all versions up to 3.7.0; no fix listed
- bolt/bolt (Packagist): affected all versions up to 3.7.0; 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-2025-34086/ (Markdown: https://insights.sbomify.com/CVE-2025-34086/index.md)
```

## Sources

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

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