How severe is GHSA-gfhp-jgp6-838j?

GHSA-gfhp-jgp6-838j has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gfhp-jgp6-838j?

GHSA-gfhp-jgp6-838j affects the following packages: CompositeC1.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-gfhp-jgp6-838j?

Update CompositeC1.Core to 6.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gfhp-jgp6-838j is resolved across your whole dependency graph.

How do I detect GHSA-gfhp-jgp6-838j in my NuGet dependencies?

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.

How do I mitigate GHSA-gfhp-jgp6-838j if there is no patch (or I can't update yet)?

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.

Is GHSA-gfhp-jgp6-838j actively exploited in the wild?

No public exploit code has been indexed for GHSA-gfhp-jgp6-838j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gfhp-jgp6-838j?

GHSA-gfhp-jgp6-838j has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gfhp-jgp6-838j?

GHSA-gfhp-jgp6-838j is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-gfhp-jgp6-838j published, and has it been updated?

GHSA-gfhp-jgp6-838j was published on September 30, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

CRITICAL severity

Orckestra C1 CMS's deserialization of untrusted data allows for arbitrary code executionGHSA-gfhp-jgp6-838j

CRITICALFix: Orckestra/C1-CMS-Foundation#814

GHSA-gfhp-jgp6-838j 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.

Also known asCVE-2022-39256

Published

Sep 30, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-gfhp-jgp6-838j.

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

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

1 pkg affected

.NETCompositeC1.Core

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`CompositeC1.Core`	all versions	6.13`dotnet add package CompositeC1.Core --version 6.13`

Affected Products

1 product · 1 configurations

Application

c1 cmsorckestra

< 6.13

range

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-gfhp-jgp6-838j 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

### 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](https://code-white.com/en/).