# CVE-2021-32650: Arbitrary code execution in october/system

> An attacker with backend access can execute arbitrary PHP code via the theme import feature, bypassing safe mode restrictions.

- **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:** Yes
- **Published:** 14 Jan 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-5hfj-r725-wpc4

## What is CVE-2021-32650?

CVE-2021-32650 is a high-severity code injection vulnerability in Octobercms October, published on 14 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

October CMS is a self-hosted content management system (CMS) platform based on the Laravel PHP Framework. Prior to versions 1.0.473 and 1.1.6, an attacker with access to the backend is able to execute PHP code by using the theme import feature. This will bypass the safe mode feature that prevents PHP execution in the CMS templates.The issue has been patched in Build 473 (v1.0.473) and v1.1.6. Those unable to upgrade may apply the patch to their installation manually as a workaround.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2021-32650?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `october/system` | Packagist | All versions | 1.0.473 |
| `october/system` | Packagist | All versions | 1.0.473 |
| `october/system` | Packagist | From 1.1.0 | 1.1.6 |
| `october/system` | Packagist | From 1.1.0 | 1.1.6 |

Products: Octobercms October.

## How do I fix CVE-2021-32650?

Upgrade october/system to a fixed version for your release line: 1.0.473 or 1.1.6.

## Is CVE-2021-32650 being exploited?

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

## Other vulnerabilities in Octobercms October

- [CVE-2021-32648](https://insights.sbomify.com/CVE-2021-32648/): October CMS Improper Authentication (high 8.2, exploited in the wild)
- [CVE-2021-3311](https://insights.sbomify.com/CVE-2021-3311/): October CMS Session ID not invalidated after logout (critical 9.8)
- [CVE-2017-1000194](https://insights.sbomify.com/CVE-2017-1000194/): October CMS File Upload Vulnerability (critical 9.8)
- [CVE-2017-1000196](https://insights.sbomify.com/CVE-2017-1000196/): Code injection in n/a (critical 9.8)
- [CVE-2017-1000197](https://insights.sbomify.com/CVE-2017-1000197/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32650 and fix it if it is affected.

What it is: CVE-2021-32650 is a high-severity code injection vulnerability in Octobercms October, published on 14 Jan 2022. 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-2021-32650 exists.

Affected packages and fixed versions:
- october/system (Packagist): affected all versions; fixed in 1.0.473
- october/system (Packagist): affected all versions; fixed in 1.0.473
- october/system (Packagist): affected from 1.1.0; fixed in 1.1.6
- october/system (Packagist): affected from 1.1.0; fixed in 1.1.6

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

## Sources

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

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