Description
Kirby is an open-source content management system. In versions prior to 4.9.1 and 5.4.1, Kirby did not securely sanitize the contents of the list field on save, leaving it vulnerable to cross-site scripting (XSS). Kirby's list field stores its formatted content as HTML, and unlike other field types, its HTML special characters cannot be escaped without losing the formatting. Sanitization was only enforced client-side in the Panel, while the server did not sanitize the content on save. As a result, an attacker could bypass the Panel and send malicious HTML directly to Kirby's API, storing unsanitized markup in the content file. That markup would then be rendered on the site frontend and executed in the browsers of site visitors and logged-in users browsing the site, resulting in persistent XSS. This issue has been fixed in versions 4.9.1 and 5.4.1.
Published: 2026-07-16
Score: 8.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows persistent cross‑site scripting because unsanitized HTML entered into Kirby's list field is stored and later rendered on the website. Kirby's list field stores formatted content as HTML, and the server does not sanitize this field on save; only client‑side checks in the Panel exist. As a result an attacker can embed malicious JavaScript into the list, which will execute in the browsers of site visitors and logged‑in users who view the affected pages. This flaw corresponds to CWE‑79.

Affected Systems

The issue affects the Kirby content‑management system. Versions before 4.9.1 and before 5.4.1 are vulnerable; those releases include the list field that stores formatted HTML without server‑side sanitization.

Risk and Exploitability

The CVSS score of 8.5 indicates high severity, while the EPSS score below 1 % shows a very low probability of exploitation at present. The vulnerability is not listed in CISA KEV. Attackers can exploit it by sending crafted content through Kirby's API, bypassing the Panel's client‑side checks. Based on the description, it is inferred that a remote attacker able to submit requests to the API can inject malicious markup, resulting in persistent script injection that runs whenever the list field is displayed and affecting both visitors and logged‑in users.

Generated by OpenCVE AI on July 31, 2026 at 01:14 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Kirby to version 4.9.1 or 5.4.1, which includes server‑side sanitization for list fields.
  • If an upgrade is not immediately possible, remove or disable the list field type for untrusted users so that only trusted, authenticated administrators can create or edit list content.
  • Implement a custom server‑side filter to strip or escape HTML from list field submissions before saving them to the content file as a temporary workaround.

Generated by OpenCVE AI on July 31, 2026 at 01:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-5fhx-9q32-q257 Kirby CMS vulnerable to cross-site scripting (XSS) from list field content in the site frontend
History

Fri, 17 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 16 Jul 2026 22:45:00 +0000

Type Values Removed Values Added
First Time appeared Getkirby
Getkirby kirby
Vendors & Products Getkirby
Getkirby kirby

Thu, 16 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
Description Kirby is an open-source content management system. In versions prior to 4.9.1 and 5.4.1, Kirby did not securely sanitize the contents of the list field on save, leaving it vulnerable to cross-site scripting (XSS). Kirby's list field stores its formatted content as HTML, and unlike other field types, its HTML special characters cannot be escaped without losing the formatting. Sanitization was only enforced client-side in the Panel, while the server did not sanitize the content on save. As a result, an attacker could bypass the Panel and send malicious HTML directly to Kirby's API, storing unsanitized markup in the content file. That markup would then be rendered on the site frontend and executed in the browsers of site visitors and logged-in users browsing the site, resulting in persistent XSS. This issue has been fixed in versions 4.9.1 and 5.4.1.
Title Kirby: Cross-site scripting (XSS) from list field content in the site frontend
Weaknesses CWE-79
References
Metrics cvssV4_0

{'score': 8.5, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-17T13:11:28.792Z

Reserved: 2026-05-05T14:39:34.923Z

Link: CVE-2026-44175

cve-icon Vulnrichment

Updated: 2026-07-17T13:11:24.404Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T01:15:18Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')