# CVE-2022-36532: File upload in n/a

> Authenticated editors can upload and rename malicious files to achieve remote code execution in Bolt CMS.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 16 Sep 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-hmmj-pppq-vw96

## What is CVE-2022-36532?

CVE-2022-36532 is a high-severity vulnerability in n/a, published on 16 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bolt CMS contains a vulnerability in version 5.1.12 and below that allows an authenticated user with the ROLE_EDITOR privileges to upload and rename a malicious file to achieve remote code execution.

## Which versions are affected by CVE-2022-36532?

It affects 1 product.


Products: Bolt Bolt Cms.

## How do I fix CVE-2022-36532?

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

## Is CVE-2022-36532 being exploited?

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

Public exploit code:

- Proof of concept for CVE-2022-36532: RCE via File Upload in Bolt CMS 5.1.12 and below. (github_poc): https://github.com/lutrasecurity/CVE-2022-36532

## Other vulnerabilities in n/a

- [CVE-2021-40219](https://insights.sbomify.com/CVE-2021-40219/): Code Injection in Bolt CMS (high 8.8)
- [CVE-2018-19933](https://insights.sbomify.com/CVE-2018-19933/): Bolt Cross-site Scripting (XSS) via text input click preview button (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36532 and fix it if it is affected.

What it is: CVE-2022-36532 is a high-severity vulnerability in n/a, published on 16 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36532 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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