Chaingetkirby · kirbyPackagist:getkirby/cms
getkirby kirby: successive fixes (2020–2022)
4 CVEs over 2 generations, 8 Dec 2020 to 29 Aug 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2020-262558 Dec 2020 First in the chain
- CVE-2021-327352 Jul 2021 No direct link to an earlier CVE
- CVE-2021-4125216 Nov 2021 related to CVE-2021-32735related to CVE-2020-26255
- CVE-2022-3603729 Aug 2022 related to CVE-2021-32735
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2020-26255 | 8 Dec 2020 | PHP Phar archives could be uploaded and executed in Kirby · fixed in 3.4.5 | First in chain | 19.6 |
| CVE-2021-32735 | 2 Jul 2021 | Cross-site scripting (XSS) from field and configuration text displayed in the Panel · fixed in 3.5.7 | First in chain | 14.0 |
| CVE-2021-41252 | 16 Nov 2021 | Cross-site scripting (XSS) from writer field content in the site frontend · fixed in 3.5.8 | CVE-2021-32735 · related · High | 17.2 |
| CVE-2022-36037 | 29 Aug 2022 | Cross-site scripting (XSS) from dynamic options in the multiselect field in Kirby · fixed in 3.5.8.1 | CVE-2021-32735 · related · Medium | 16.2 |