CVE-2022-39256 is a critical-severity (CVSS 9) Deserialization of Untrusted Data vulnerability in CompositeC1.Core. A fix is available for CompositeC1.Core — see the affected versions and patch details below.
Orckestra C1 CMS's deserialization of untrusted data allows for arbitrary code execution.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-39256.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
CompositeC1.CoreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Orckestra C1 CMS. Authentication is required to exploit this vulnerability. The authenticated user may perform the actions unknowingly by visiting a specially crafted site.
Patches
Patched in C1 CMS v6.13
Workarounds
Upgrade to C1 CMS v6.13 or newer is required
Credit
This issue was discovered and reported by Markus Wulftange / Code White GmbH.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | CompositeC1.Core | all versions | 6.13dotnet add package CompositeC1.Core --version 6.13 |
Affected Products
c1 cmsorckestraDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CompositeC1.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update CompositeC1.Core to 6.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39256 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2022-39256 in your dependencies?
Find it across NuGet, including transitive dependencies.