# CVE-2019-18211: Deserialization in n/a

> Unvalidated deserialization in C1 CMS allows low-privilege users to execute arbitrary code remotely.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-76qf-3cvm-8qwq

## What is CVE-2019-18211?

CVE-2019-18211 is a high-severity unsafe deserialization vulnerability in n/a, published on 23 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Orckestra C1 CMS through 6.6. The EntityTokenSerializer class in Composite.dll is prone to unvalidated deserialization of wrapped BinaryFormatter payloads, leading to arbitrary remote code execution for any low-privilege user.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2019-18211?

It affects 1 product.


Products: Orckestra C1 Cms.

## How do I fix CVE-2019-18211?

No fix has been published for CVE-2019-18211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-18211 being exploited?

There is no known exploitation of CVE-2019-18211 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-39256](https://insights.sbomify.com/CVE-2022-39256/): Orckestra C1 CMS's deserialization of untrusted data allows for arbitrary code execution. (critical 9.0)
- [CVE-2021-34992](https://insights.sbomify.com/CVE-2021-34992/): Deserialization in C1 CMS (high 8.8)
- [CVE-2022-24789](https://insights.sbomify.com/CVE-2022-24789/): Deserialization of untrusted data in C1 CMS. (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18211 and fix it if it is affected.

What it is: CVE-2019-18211 is a high-severity unsafe deserialization vulnerability in n/a, published on 23 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18211 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-18211/ (Markdown: https://insights.sbomify.com/CVE-2019-18211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-18211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-18211
- OSV: https://osv.dev/vulnerability/CVE-2019-18211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-18211/
Summaries are generated and may contain mistakes; the official description above is the record.