Is getkirby/panel 2.4 vulnerable?
Composer · 3 releases from 2.4.0 to 2.4.2 · latest getkirby/panel is 2.5.14 · checked 19 Nov 2026
Yes: 2 known advisories
Yes. getkirby/panel 2.4.2, the last 2.4 release, is affected by 2 known security advisories (2 medium), including CVE-2020-26253, CVE-2020-26255. Upgrade to 2.5.14 or later to fix all of them.
composer require getkirby/panel:^2.5.14Is your project on an affected getkirby/panel?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting getkirby/panel 2.4.2
Kirby .dev domains and some reverse proxy setups were treated as local
- Affected
- <2.5.14
- Fixed in
- 2.5.14
Kirby Panel users could upload PHP Phar archives as content files before v2.5.14 and v3.4.5
- Affected
- <2.5.14
- Fixed in
- 2.5.14
Every getkirby/panel 2.4.x release
Affected: 2.4.0 to 2.4.2. Latest getkirby/panel: 2.5.14.
| Version | Known advisories |
|---|---|
| getkirby/panel 2.4.2 | CVE-2020-26253, CVE-2020-26255 |
| getkirby/panel 2.4.1 | CVE-2020-26253, CVE-2020-26255 |
| getkirby/panel 2.4.0 | CVE-2020-26253, CVE-2020-26255 |
Which of your client projects are still on getkirby/panel 2.4?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact getkirby/panel version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other getkirby/panel versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.