Vulnerability in getkirby/cms (CVE-2026-42051)
Summary
Vulnerability in getkirby/cms (CVE-2026-42051). Risk of unauthorized operations or information disclosure. Exploitable via access.system. 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, the system API endpoint leaks license data and installed version to authenticated users. 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-42051 has been found in getkirby/cms.
Attackers can target a specific entry point like access.system over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/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-42051" on the vendor's site.
CVE-2026-42051 (getkirby/cms) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: access.system
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 access.system.
Check the vendor advisory for the affected versions of getkirby/cms. Attack surface: access.system.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
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