CVE-2026-32870: Kirby has XML injection in its XML creator toolkit
TL;DR This vulnerability only affects Kirby sites that use the Xml data handler (e.g. Data::encode($string, 'xml')) or the Xml::create(), Xml::tag() or Xml::value() method(s) in site or plugin code. The Kirby core does not use any of the affected methods.
Published Apr 23, 2026 · Updated Apr 27, 2026
Affected packages
getkirby/cms
- Ecosystem
- Composer (PHP)
- Affected
- < 4.9.0
- Fixed in
- 4.9.0
- Check
composer show getkirby/cms
getkirby/cms
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.0.0, < 5.4.0
- Fixed in
- 5.4.0
- Check
composer show getkirby/cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
TL;DR
This vulnerability only affects Kirby sites that use the Xml data handler (e.g. Data::encode($string, 'xml')) or the Xml::create(), Xml::tag() or Xml::value() method(s) in site or plugin code. The Kirby core does not use any of the affected methods.
If consumers use an affected method and cannot rule out input to these methods controlled by an attacker, Kirby strongly recommends that they update to a patch release.
----
Introduction
XML strings contain structured data in tags and attributes. Depending on the used XML schema, this data can carry specific meaning that can lead to actions in other systems that parse and act on the XML data. Tags and attributes are detected based on their specific syntax, which includes characters such as <, >, ", and &. If these characters are to be used verbatim in text within the XML string, they can be escaped using a <![CDATA[ ]]> block.
XML injection is an attack on a system generating or parsing XML files. By injecting special characters into input data, XML output with a malicious meaning could be generated by a vulnerable system.
Impact
Kirby's Xml::value() method has special handling for <![CDATA[ ]]> blocks. If the input value is already valid CDATA, it is not escaped a second time but allowed to pass through. However it was possible to trick this check into allowing values that only *contained* a valid CDATA block but also contained other structured data outside of the CDATA block. This structured data would then also be allowed to pass through, circumventing the value protection.
The Xml::value() method is used in Xml::tag(), Xml::create() and in the Xml data handler (e.g. Data::encode($string, 'xml')).
Both the vulnerable methods and the data handler are not used in the Kirby core. However they may be used in site or plugin code, e.g. to create XML strings from input data. If those generated files are passed to another implementation that assigns specific meaning to the XML schema, manipulation of this system's behavior is possible.
Kirby sites that don't use XML generation in site or plugin code are *not* affected.
Patches
The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. Please update to one of these or a later version to fix the vulnerability.
In all of the mentioned releases, Kirby has added additional checks that only allow unchanged CDATA passthrough if the entire string is made up of valid CDATA blocks and no structured data. This protects all uses of the method against the described vulnerability.
Credits
Kirby thanks to Patrick Falb (@dapatrese) at FORMER 03 for responsibly reporting the identified issue.
Credited to dapatrese.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-75592
Kirby: Access to image files outside of the site root via path traversal in the media handling
medium6.9Sep 2, 2026CVE-2026-69127
Kirby: System path exposure from error messages in the REST API
medium6.9Sep 1, 2026CVE-2026-71415
Kirby: File upload permissions are not checked during processing of chunk data
high7.1Aug 31, 2026CVE-2026-75594
Kirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media handling
high8.2Aug 31, 2026CVE-2026-49274
Kirby: `pages.access` permission is not checked in the pages picker for parent pages
medium5.3Jun 18, 2026CVE-2026-49276
Kirby: Self cross-site scripting (self-XSS) in the writer field
high7.4Jun 18, 2026
