CVE-2026-54003: Kirby External Initialization Of The Panel Vulnerability

CRITICAL
Advisory Identifier: GHSA-whxw-24jc-cwmv
CWE-454
Published
Advisory Summary

CVE-2026-54003 is a CRITICAL external initialization of the panel vulnerability (CWE-454: External Initialization of Trusted Variables or Data Stores) affecting Kirby libraries in the Packagist ecosystem. The issue involves external initialization of the panel on reverse proxy setups with the `forwarded` header. Remediation is available by upgrading affected packages to version 4.9.4, 5.4.4.

CVE-2026-54003 at a Glance

CVE Identifier CVE-2026-54003
GHSA Identifier GHSA-whxw-24jc-cwmv
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-454: External Initialization of Trusted Variables or Data Stores
Affected Product Kirby
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-54003

To remediate this vulnerability, upgrade all affected Kirby dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

getkirby/cms fixed: 4.9.4
Upgrade getkirby/cms to 4.9.4
getkirby/cms fixed: 5.4.4
Upgrade getkirby/cms to 5.4.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for getkirby/cms

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-54003, inspect your project dependencies for Kirby:

inspect dependencies for getkirby/cms

Analyze the terminal output to locate any version of Kirby in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.9.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-454: External Initialization of Trusted Variables or Data Stores, where the product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors. In Kirby, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### TL;DR This vulnerability affects Kirby sites that have no configured user accounts and are running on publicly accessible servers behind a reverse proxy that sets the `Forwarded: for=...`, `X-Client-IP`, or `X-Real-IP` request header. It was possible to install the Panel (= create the first admin user) in these setups even from remote IP addresses. **This vulnerability is of critical severity for affected sites.** Your site is *not* affected if any of the following apply: - An admin account has already been configured - The Panel and API are disabled - The site is not running behind a reverse proxy - The reverse proxy sets the `X-Forwarded-For` or `Client-IP` header instead of the affected ones. ---- ### Introduction External Initialization is a type of vulnerability that allows attackers to initialize a system or configuration value without authentication. This can give untrusted actors access to the system or let them control its behavior. ### Affected components The Kirby Panel and REST API are authenticated by local user accounts. If a Kirby installation does not yet have any users, it first needs to be installed. During the installation process, an initial admin user account is created. To protect against external initialization attacks that would allow untrusted actors to create an admin user for the Kirby installation, Kirby already checked whether the current request came from a local IP address. This allows installing the Panel in local development setups. Installation on remote servers was only supposed to be possible when the `panel.install` configuration option was enabled. The `isLocal` check takes all relevant request headers into account and treats a request as non-local as soon as any checked request header contains an external IP address. ### Impact In affected releases, the `isLocal` check for the installation logic did not properly take the `Forwarded: for=...` header into account. This header is set by modern reverse proxy servers. It also did not take into account the `X-Client-IP` or `X-Real-IP` headers, which are set by some custom reverse proxy setups. This caused Kirby to falsely assume that an installation request was local and allowed creating an admin account even though the reverse proxy forwarded the request from an external IP address. Reverse proxies setting the `X-Forwarded-For` or `Client-IP` headers were *not* affected. These headers were already properly checked for external IP addresses. ### Patches The problem has been patched in [Kirby 4.9.4](https://github.com/getkirby/kirby/releases/tag/4.9.4) and [Kirby 5.4.4](https://github.com/getkirby/kirby/releases/tag/5.4.4). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability. In all of the mentioned releases, we fixed the `isLocal` check to also properly take `Forwarded: for=...`, `X-Client-IP` and `X-Real-IP` request headers into account. ### Workarounds Sites on older Kirby versions (Kirby 3 starting at 3.7.0) can be protected with one of the following workarounds: - Perform the Panel installation yourself by creating an initial admin account. As soon as one or more accounts are present, the vulnerable installation code is no longer active. - If you don't need the Panel, disable the REST API with the `'api' => false` option in `config.php`. ### Credits Thanks to Peter Levashov (@petersevera) for responsibly reporting the identified issue.

CVE-2026-54003 Affected Kirby Versions

2 component(s)
Fixed Versions:
4.9.45.4.4
Product / Package Ecosystem Affected Versions Fixed Version
getkirby/cms
Packagist
< 4.9.4
4.9.4
getkirby/cms
Packagist
≥ 5.0.0-alpha.1
< 5.4.4
5.4.4

References

Frequently Asked Questions

What is CVE-2026-54003?
CVE-2026-54003 is a security vulnerability in Kirby involving External Initialization of the Panel on reverse proxy setups with the `Forwarded` header under CWE-454: External Initialization of Trusted Variables or Data Stores.
Which Kirby versions are affected?
Affected versions include releases prior to 4.9.4, 5.4.4 across affected packages: getkirby/cms.
What version fixes CVE-2026-54003?
Upgrading to 4.9.4, 5.4.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is getkirby/cms affected?
Yes, getkirby/cms is affected in releases prior to 4.9.4, 5.4.4. Upgrade your dependency to 4.9.4, 5.4.4 or later.
What CWE is associated with CVE-2026-54003?
CVE-2026-54003 is classified under CWE-454: External Initialization of Trusted Variables or Data Stores (The product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.).
How can I check Packagist dependencies for CVE-2026-54003?
Run the dependency tree command: 'inspect dependencies for getkirby/cms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-whxw-24jc-cwmv",
  "modified" : "2026-06-18T15:04:57Z",
  "published" : "2026-06-18T15:04:57Z",
  "aliases" : [ "CVE-2026-54003" ],
  "summary" : "Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header",
  "details" : "### TL;DR\n\nThis vulnerability affects Kirby sites that have no configured user accounts and are running on publicly accessible servers behind a reverse proxy that sets the `Forwarded: for=...`, `X-Client-IP`, or `X-Real-IP` request header.\n\nIt was possible to install the Panel (= create the first admin user) in these setups even from remote IP addresses.\n\n**This vulnerability is of critical severity for affected sites.**\n\nYour site is *not* affected if any of the following apply: \n\n- An admin account has already been configured\n- The Panel and API are disabled\n- The site is not running behind a reverse proxy\n- The reverse proxy sets the `X-Forwarded-For` or `Client-IP` header instead of the affected ones.\n\n----\n\n### Introduction\n\nExternal Initialization is a type of vulnerability that allows attackers to initialize a system or configuration value without authentication.\n\nThis can give untrusted actors access to the system or let them control its behavior.\n\n### Affected components\n\nThe Kirby Panel and REST API are authenticated by local user accounts. If a Kirby installation does not yet have any users, it first needs to be installed. During the installation process, an initial admin user account is created.\n\nTo protect against external initialization attacks that would allow untrusted actors to create an admin user for the Kirby installation, Kirby already checked whether the current request came from a local IP address. This allows installing the Panel in local development setups. Installation on remote servers was only supposed to be possible when the `panel.install` configuration option was enabled.\n\nThe `isLocal` check takes all relevant request headers into account and treats a request as non-local as soon as any checked request header contains an external IP address.\n\n### Impact\n\nIn affected releases, the `isLocal` check for the installation logic did not properly take the `Forwarded: for=...` header into account. This header is set by modern reverse proxy servers. It also did not take into account the `X-Client-IP` or `X-Real-IP` headers, which are set by some custom reverse proxy setups.\n\nThis caused Kirby to falsely assume that an installation request was local and allowed creating an admin account even though the reverse proxy forwarded the request from an external IP address.\n\nReverse proxies setting the `X-Forwarded-For` or `Client-IP` headers were *not* affected. These headers were already properly checked for external IP addresses.\n\n### Patches\n\nThe problem has been patched in [Kirby 4.9.4](https://github.com/getkirby/kirby/releases/tag/4.9.4) and [Kirby 5.4.4](https://github.com/getkirby/kirby/releases/tag/5.4.4). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability.\n\nIn all of the mentioned releases, we fixed the `isLocal` check to also properly take `Forwarded: for=...`, `X-Client-IP` and `X-Real-IP` request headers into account.\n\n### Workarounds\n\nSites on older Kirby versions (Kirby 3 starting at 3.7.0) can be protected with one of the following workarounds:\n\n- Perform the Panel installation yourself by creating an initial admin account. As soon as one or more accounts are present, the vulnerable installation code is no longer active.\n- If you don't need the Panel, disable the REST API with the `'api' => false` option in `config.php`.\n\n### Credits\n\nThanks to Peter Levashov (@petersevera) for responsibly reporting the identified issue.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "getkirby/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.9.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.9.3"
    }
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "getkirby/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0-alpha.1"
      }, {
        "fixed" : "5.4.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.4.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/security/advisories/GHSA-whxw-24jc-cwmv"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/getkirby/kirby"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/releases/tag/4.9.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/releases/tag/5.4.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-454" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-18T15:04:57Z",
    "nvd_published_at" : null
  }
}