Attack Chain

1. An authenticated attacker logs into the Kirby CMS Panel with legitimate credentials.
2. The attacker navigates to an editable content field, such as a writer or list field, or interacts with a custom plugin using the Sane API functions ($dom->sanitize(), Sane::sanitizeFile(), etc.).
3. The attacker crafts and injects malicious markup, specifically including JavaScript code (e.g., <script>alert('XSS')</script>) as children of an unknown HTML/XML tag (e.g., <foo><script>alert(1)</script></foo>).
4. The Kirby backend processes the submitted content, invoking the vulnerable Dom::sanitize() method.
5. Due to the flaw, Dom::sanitize() unwraps the unknown parent tag but fails to sanitize the malicious child nodes, allowing the JavaScript payload to be saved unsanitized into the content data.
6. Another user, potentially a higher-privileged administrator, accesses the Panel or frontend page where the maliciously injected content is displayed.
7. The victim's web browser renders the unsanitized content, leading to the execution of the injected JavaScript within their session context.
8. The executed script can steal session cookies, perform unauthorized actions via Kirby's API (e.g., privilege escalation), redirect the user, or deface the interface, compromising the victim's account and potentially the entire CMS.

Impact

The vulnerability poses a significant risk to affected Kirby CMS installations, particularly those with multiple authenticated users where some may be untrusted or malicious. Successful exploitation allows for stored XSS, meaning the injected JavaScript persists and executes each time the compromised content is viewed. This can lead to privilege escalation, enabling lower-privileged authenticated users to escalate their access by compromising higher-privileged user sessions (e.g., administrators). The impact can range from session hijacking, data exfiltration through unauthorized API calls to Kirby's backend, to defacement or other client-side attacks affecting any user viewing the malicious content. The advisory notes that content stored before patching may still contain malicious payloads, emphasizing the persistent nature of the threat.

Recommendation

• Patch CVE-2026-54002: Immediately update Kirby CMS to version 4.9.4, 5.4.4, or a later release to remediate the sanitization flaw.
• Review and Re-sanitize Content: If untrusted authenticated users had access to the Kirby Panel on a security-critical site, review and re-sanitize all existing content that may have passed through affected fields (e.g., writer, list fields, or custom code using Sane API) for potential malicious payloads.
• Deploy Sigma Rule for XSS Attempts: Deploy the Detect CVE-2026-54002 XSS Injection in Kirby Panel Sigma rule to your webserver logs (category webserver) to identify attempts to inject XSS payloads into Kirby content fields.
• Implement WAF/API Security: Implement a Web Application Firewall (WAF) or API security gateway to block requests containing known XSS patterns targeting CMS editing endpoints, acting as an additional layer of defense.