Server side request forgery in C1 CMS

Exploitation

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

CVSS

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

EPSS

• CVE-2022-24789: 0.76% estimated exploitation activity in the next 30 days; percentile 55.46 (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.

C1 CMS is an open-source, .NET based Content Management System (CMS). Versions prior to 6.12 allow an authenticated user to exploit Server Side Request Forgery (SSRF) by causing the server to make arbitrary GET requests to other servers in the local network or on localhost. The attacker may also truncate arbitrary files to zero size (effectively delete them) leading to denial of service (DoS) or altering application logic. The authenticated user may unknowingly perform the actions by visiting a specially crafted site. Patched in C1 CMS v6.12, no known workarounds exist.

Published by the source

30 Mar 2022, 00:00 UTC

Last modified by the source

27 Jan 2023, 05:01 UTC

Source last checked

26 Oct 2026, 16:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8pp6-8x4q-c5mx

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

# Patch Next advisory brief: CVE-2022-24789

Advisory: Server side request forgery in C1 CMS
IDs: CVE-2022-24789, GHSA-8pp6-8x4q-c5mx
Record: https://patchnext.com/advisories/cve-2022-24789 (revision 1, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: c1cms.assemblies 6.12.8122.18346. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet c1cms.assemblies: affected <= 6.11.7982.26191; fixed in 6.12.8122.18346

## Suggested inspection (read-only)
- NuGet c1cms.assemblies: 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 c1cms.assemblies.
- 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-8pp6-8x4q-c5mx (GitHub-reviewed advisory GHSA-8pp6-8x4q-c5mx lists affected ranges: NuGet c1cms.assemblies >=0 <=6.11.7982.26191)

Commands are suggestions: review each one before running it.