Vulnerability in getkirby/cms (CVE-2021-32735)
Summary
Vulnerability in getkirby/cms (CVE-2021-32735). Risk of unauthorized operations or information disclosure. Exploitable via ListItem. Mitigation: upgrade to 3.5.7 or later.
Original description
The description as published by the source.
Kirby is a content management system. In Kirby CMS versions 3.5.5 and 3.5.6, the Panel's ListItem component (used in the pages and files section for example) displayed HTML in page titles as it is. This could be used for cross-site scripting (XSS) attacks. Malicious authenticated Panel users can escalate their privileges if they get access to the Panel session of an admin user. Visitors without Panel access can use the attack vector if the site allows changing site data from a frontend form. Kirby 3.5.7 patches the vulnerability. As a partial workaround, site administrators can protect against attacks from visitors without Panel access by validating or sanitizing provided data from the frontend form.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2021-32735 has been found in getkirby/cms.
Attackers can target a specific entry point like ListItem over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade getkirby/cms to 3.5.7 or later.
If unsure, ask your IT team or search "getkirby/cms CVE-2021-32735" on the vendor's site.
CVE-2021-32735 (getkirby/cms) — CWE-80
Attack vector: remote (network-reachable)
Attack surface: ListItem
Patched: 3.5.7 — 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-80) exists in getkirby/cms. Attackers reach the vulnerable code path via ListItem.
Check the vendor advisory for the affected versions of getkirby/cms. Attack surface: ListItem.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.5.7.
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 3.5.7ステージング環境で 3.5.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com