Missing server signature validation in OctoberCMS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-23655: 0.64% estimated exploitation activity in the next 30 days; percentile 50.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This advisory affects authors of plugins and themes listed on the October CMS marketplace where an end-user will inadvertently expose authors to potential financial loss by entering their private license key into a compromised server. It has been disclosed that a project fork of October CMS v1.0 is using a compromised gateway to access the October CMS marketplace service. The compromised gateway captures the personal/business information of users and authors, including private source code files. It was also disclosed that captured plugin files are freely redistributed to other users without authorization. 1. End-users are provided with a forked version of October CMS v1.0. The provided software is modified to use a compromised gateway server. 2. The user is instructed to enter their October CMS license key into the administration panel to access the October CMS marketplace. The key is sent to the compromised server while appearing to access the genuine October CMS gateway…

Published by the source

24 Feb 2022, 13:09 UTC

Last modified by the source

3 Feb 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-53m6-44rc-h2q5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-23655

Advisory: Missing server signature validation in OctoberCMS
IDs: CVE-2022-23655, GHSA-53m6-44rc-h2q5
Record: https://patchnext.com/advisories/cve-2022-23655 (revision 1, source checked 26 Oct 2026, 14:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: october/system 1.1.11, 1.0.475. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist october/system: affected >= 1.1.0, < 1.1.11; < 1.0.475; fixed in 1.1.11, 1.0.475

## Suggested inspection (read-only)
- Packagist october/system: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on october/system.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-53m6-44rc-h2q5 (GitHub-reviewed advisory GHSA-53m6-44rc-h2q5 lists affected ranges: Packagist october/system >=1.1.0 =0 <1.0.475)

Commands are suggestions: review each one before running it.