CompositeC1.Core Known Vulnerabilities & Fixes
CompositeC1.Core has 1 known security vulnerability in NuGet (.NET). Upgrade to version 6.13 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 6.13
Upgrading to 6.13 or later resolves all 1 known vulnerability in CompositeC1.Core. Run: dotnet add package CompositeC1.Core --version 6.13
Is CompositeC1.Core in your project?
Check if you're affected and upgrade to 6.13 to stay secure.
Security Summary
- 1 affected version range has been identified across this advisory.
- 100% of known issue has a published fixed version.
- Remediation: dotnet add package CompositeC1.Core
Vulnerabilities
1 unique vulnerability — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2022-39256 Orckestra C1 CMS's deserialization of untrusted data allows for arbitrary code execution. | CRITICAL | 4.2.0, 4.2.1, 4.3.0, 4.3.0-beta1 (+19 more) | 6.13 |
About This Data
Vulnerability data for CompositeC1.Core is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related NuGet (.NET) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of CompositeC1.Core.