CVE-2019-11080 in the critical feed json
Sitecore Experience Platform (XP) prior to 9.1.1 is vulnerable to remote code execution via deserialization, aka TFS # 293863.
published 7y ago modified 4mo ago also EUVD-2019-2785
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.9%
- EPSS 13.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Sitecore Experience Platform (XP) prior to 9.1.1 is vulnerable to remote code execution via deserialization, aka TFS # 293863. An authenticated user with necessary permissions is able to remotely execute OS commands by sending a crafted serialized object.
Patch / fix
- sitecore experience_platform 9.1.1
Is CVE-2019-11080 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-46987)
Exploit prediction
13.95% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46987 Sitecore 8.x - Deserialization Remote Code Execution webapps, 2019-06-13
- github.com https://github.com/minecrater/exploits/blob/master/Sitecore8xDeserialRCE referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/minecrater/exploits/blob/master/Sitecore8xDeserialRCE
exploit, third-party-advisory
-
dev.sitecore.net
/Downloads/Sitecore%20Experience%20Platform/91/Sitecore%20Experience%20Platform%2091%20Update1/Release%20Notes
release-notes, vendor-advisory
- packetstormsecurity.com /files/153274/Sitecore-8.x-Deserialization-Remote-Code-Execution.html
Sources
- CVE List CVE-2019-11080
- NVD CVE-2019-11080
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.