# CVE-2022-23655: Missing server signature validation in OctoberCMS

> Attackers can use non-authoritative gateway servers to exfiltrate user private keys due to missing server signature validation in OctoberCMS.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A: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:** Yes
- **Published:** 23 Feb 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-53m6-44rc-h2q5

## What is CVE-2022-23655?

CVE-2022-23655 is a medium-severity missing authorization vulnerability in Octobercms October, published on 23 Feb 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Octobercms is a self-hosted CMS platform based on the Laravel PHP Framework. Affected versions of OctoberCMS did not validate gateway server signatures. As a result non-authoritative gateway servers may be used to exfiltrate user private keys. Users are advised to upgrade their installations to build 474 or v1.1.10. The only known workaround is to manually apply the patch (e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a) which adds server signature validation.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

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.475 |
| `october/system` | Packagist | All versions | 1.0.475 |
| `october/system` | Packagist | From 1.1.0 | 1.1.11 |
| `october/system` | Packagist | From 1.1.0 | 1.1.11 |

Products: Octobercms October.

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

Upgrade october/system to a fixed version for your release line: 1.0.475 or 1.1.11.

## Is CVE-2022-23655 being exploited?

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

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

What it is: CVE-2022-23655 is a medium-severity missing authorization vulnerability in Octobercms October, published on 23 Feb 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23655 in the wild and no public exploit code.

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

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

## Sources

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

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