getkirby/panel vulnerabilities

The Kirby 2 panel.

Registry
Composer
Latest
2.5.14
License
proprietary

2 known advisories

The latest version, 2.5.14, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require getkirby/panel:^2.5.14

Is your project on an affected getkirby/panel?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for getkirby/panel

  • MediumCVE-2020-26253GHSA-2ccx-2gf3-8xvv14 Jan 2021

    Kirby .dev domains and some reverse proxy setups were treated as local

    Affected
    <2.5.14
    Fixed in
    2.5.14
  • MediumCVE-2020-26255GHSA-g3h8-cg9x-47qw8 Dec 2020

    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

Is your getkirby/panel version vulnerable?

Which of your client projects still run an old getkirby/panel?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.