Categories
CVE-2026-44176

Vulnerability in getkirby/cms (CVE-2026-44176)

Summary

Vulnerability in getkirby/cms (CVE-2026-44176). Risk of unauthorized operations or information disclosure. Exploitable via pages.access. Mitigation: upgrade to 5.4.1 or later.

Original description

The description as published by the source.

Kirby is an open-source content management system. Versions prior to 4.9.1 and 5.4.1 do not check the pages.access permission during page draft rendering. Permissions are defined for each user role in the user blueprint (site/blueprints/users/...). It is also possible to customize the permissions for each target model in the model blueprints (such as in site/blueprints/pages/...) using the options feature. The permissions and options together control the authorization of user actions. Kirby provides the pages.access and pages.list permissions (among others). The list permission controls whether affected models appear in lists throughout the Panel and REST API. The access permission has the same effect but also disables direct access to the affected models. This vulnerability affects the path resolver for the main CMS router. The resolver takes an input path from the requested URL and determines which model (page or file) should be rendered. When a path is requested that points to a page draft, the resolver checks that the request either contains a valid preview token or is authenticated by a valid user. In affected releases, Kirby allowed page drafts to be rendered if any valid user was authenticated, even if that user did not have access to the specific page model. Authenticated attackers with knowledge of the full path to an existing page draft could then access the rendered frontend page. This could lead to the disclosure of sensitive information, e.g. ahead of the laun…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44176 has been found in getkirby/cms.
Attackers can target a specific entry point like pages.access over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade getkirby/cms to 5.4.1 or later.
If unsure, ask your IT team or search "getkirby/cms CVE-2026-44176" on the vendor's site.

CVE-2026-44176 (getkirby/cms) — CWE-862
Attack surface: pages.access / options / pages.list / list
Patched: 5.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in getkirby/cms. Attackers reach the vulnerable code path via pages.access.

📍 Affected scope

Check the vendor advisory for the affected versions of getkirby/cms. Attack surface: pages.access / options / pages.list / list.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.4.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'getkirby/cms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'getkirby/cms' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で getkirby/cms を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade getkirby/cms to 5.4.1

    ステージング環境で 5.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer getkirby/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.1"}]}]
Packagist getkirby/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.4.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details