Vulnerability in getkirby/cms (CVE-2026-42069)
Summary
Vulnerability in getkirby/cms (CVE-2026-42069). Confidential information can be exposed externally. Exploitable via options. Mitigation: upgrade to 5.4.0 or later.
Original description
The description as published by the source.
Kirby is an open-source content management system. Prior to versions 4.9.0 and 5.4.0, read access to site, user and role information is not gated by permissions. This issue has been patched in versions 4.9.0 and 5.4.0.
Source: NIST National Vulnerability Database 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-42069 has been found in getkirby/cms.
Attackers can target a specific entry point like options over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade getkirby/cms to 5.4.0 or later.
If unsure, ask your IT team or search "getkirby/cms CVE-2026-42069" on the vendor's site.
CVE-2026-42069 (getkirby/cms) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: options / site.access / user.access / users.access
Patched: 5.4.0 — 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.
A vulnerability (CWE-862) exists in getkirby/cms. Attackers reach the vulnerable code path via options.
Check the vendor advisory for the affected versions of getkirby/cms. Attack surface: options / site.access / user.access / users.access.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 5.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'getkirby/cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
getkirby/cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade getkirby/cms to 5.4.0ステージング環境で 5.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com