# CVE-2022-21705: Authenticated remote code execution in octobercms

> Authenticated users with page management permissions can bypass safe mode to execute arbitrary code in October CMS.

- **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 Feb 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-79jw-2f46-wv22

## What is CVE-2022-21705?

CVE-2022-21705 is a high-severity code injection vulnerability in Octobercms October, published on 23 Feb 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Octobercms is a self-hosted CMS platform based on the Laravel PHP Framework. In affected versions user input was not properly sanitized before rendering. An authenticated user with the permissions to create, modify and delete website pages can exploit this vulnerability to bypass `cms.safe_mode` / `cms.enableSafeMode` in order to execute arbitrary code. This issue only affects admin panels that rely on safe mode and restricted permissions. To exploit this vulnerability, an attacker must first have access to the backend area. The issue has been patched in Build 474 (v1.0.474) and v1.1.10. Users unable to upgrade should apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe to your installation manually.

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

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

6 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.474 |
| `october/system` | Packagist | All versions | 1.0.474 |
| `october/system` | Packagist | From 1.1.0 | 1.1.10 |
| `october/system` | Packagist | From 1.1.0 | 1.1.10 |
| `october/system` | Packagist | From 2.0.0 | 2.1.27 |
| `october/system` | Packagist | From 2.0.0 | 2.1.27 |

Products: Octobercms October.

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

Upgrade october/system to a fixed version for your release line: 1.0.474, 1.1.10 or 2.1.27.

## Is CVE-2022-21705 being exploited?

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

Public exploit code:

- October CMS - Remote Code Execution (nuclei): http/cves/2022/CVE-2022-21705.yaml

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

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

Affected packages and fixed versions:
- october/system (Packagist): affected all versions; fixed in 1.0.474
- october/system (Packagist): affected all versions; fixed in 1.0.474
- october/system (Packagist): affected from 1.1.0; fixed in 1.1.10
- october/system (Packagist): affected from 1.1.0; fixed in 1.1.10
- october/system (Packagist): affected from 2.0.0; fixed in 2.1.27
- october/system (Packagist): affected from 2.0.0; fixed in 2.1.27

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

## Sources

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

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