# CVE-2019-10068: Kentico Xperience Deserialization of Untrusted Data

> Unauthenticated attackers can achieve remote code execution on Kentico servers by sending crafted requests to the staging service, bypassing authentication and triggering unsafe deserialization.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-f7w4-79f7-fhp3

## What is CVE-2019-10068?

CVE-2019-10068 is a critical unsafe deserialization vulnerability in Kentico Xperience, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Kentico 12.0.x before 12.0.15, 11.0.x before 11.0.48, 10.0.x before 10.0.52, and 9.x versions. Due to a failure to validate security headers, it was possible for a specially crafted request to the staging service to bypass the initial authentication and proceed to deserialize user-controlled .NET object input. This deserialization then led to unauthenticated remote code execution on the server where the Kentico instance was hosted.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Kentico Xperience.

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

No fix has been published for CVE-2019-10068 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2019-10068 being exploited?

Yes. Attackers have exploited CVE-2019-10068 in the wild since at least 25 Mar 2022.

Public exploit code:

- Kentico CMS Staging SyncServer Unserialize Remote Command Execution (metasploit)
- Proof of concept exploit for CVE-2019-10068. (github_poc): https://github.com/crukz404/CVE-2019-10068-PoC
- Kentico CMS Insecure Deserialization Remote Code Execution (nuclei): http/cves/2019/CVE-2019-10068.yaml

## Other vulnerabilities in Kentico Xperience

- [CVE-2025-2746](https://insights.sbomify.com/CVE-2025-2746/): Kentico Xperience CMS Authentication Bypass Using an Alternate Path or Channel (critical 9.8, exploited in the wild)
- [CVE-2025-2747](https://insights.sbomify.com/CVE-2025-2747/): Kentico Xperience CMS Authentication Bypass Using an Alternate Path or Channel (critical 9.8, exploited in the wild)
- [CVE-2025-2749](https://insights.sbomify.com/CVE-2025-2749/): Kentico Xperience Path Traversal (high 7.2, exploited in the wild)
- [CVE-2017-17736](https://insights.sbomify.com/CVE-2017-17736/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-12102](https://insights.sbomify.com/CVE-2019-12102/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10068 is a critical unsafe deserialization vulnerability in Kentico Xperience, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-10068 in the wild since at least 25 Mar 2022.

Affected product: Kentico Xperience. 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-10068/ (Markdown: https://insights.sbomify.com/CVE-2019-10068/index.md)
```

## Sources

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

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