CVE-2026-54002: getkirby kirby · Cross-site Scripting
Affects getkirby kirbySource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 5.4.4 or 4.9.4 soon.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.4.4, 4.9.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade kirby and getkirby/kirby to 5.4.4 or 4.9.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getkirbykirby | Affected
| Fixed in
|
| getkirbykirby | Affected
| Fixed in
|
GitHubgetkirby/kirbypkg:github/getkirby/kirbyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected Kirby installations to version 4.9.4 or 5.4.4 or later, where the vulnerability is fixed. No other official remediation or temporary fixes are indicated. Patch status is confirmed by the vendor advisory stating the issue is fixed in these versions.
Description
Kirby is an open-source content management system. Prior to 4.9.4 and 5.4.4, Kirby sites and plugins that use the writer or list fields or call Dom::sanitize(), Sane::sanitize(), Sane::Html::sanitize(), Sane::Svg::sanitize(), Sane::Xml::sanitize(), Sane::sanitizeFile(), or file sanitizeContents() with untrusted input allow malicious markup injected as children of an unknown HTML or XML tag to pass through Dom::sanitize() without being correctly sanitized, causing stored cross-site scripting. This issue is fixed in versions 4.9.4 and 5.4.4.
References
- github.com/getkirby/kirby/security/advisories/GHSA-wr9h-4r83-f4v6 (opens in a new tab)
- github.com/getkirby/kirby/commit/0f0437b5128c910103cbc78fc34d94b2a3faef4c (opens in a new tab)
- github.com/getkirby/kirby/commit/7ad76cf9c7387462828e6ebfc8404e31b37829e9 (opens in a new tab)
- github.com/getkirby/kirby/commit/9ec1873864441dbc06479ef7823da348ec7f2700 (opens in a new tab)
- github.com/getkirby/kirby/commit/bb2562e16c754493a403b8df84c9883108871e4c (opens in a new tab)
- github.com/getkirby/kirby/releases/tag/4.9.4 (opens in a new tab)
- github.com/getkirby/kirby/releases/tag/5.4.4 (opens in a new tab)