Improper Neutralization of Special Elements Used in a Template Engine Affecting getkirby/cms package, versions >=3.8.0-rc.1, <4.9.0>=5.0.0-alpha.1, <5.4.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PHP-GETKIRBYCMS-16300165
- published26 Apr 2026
- disclosed24 Apr 2026
- creditUnknown
Introduced: 24 Apr 2026
NewCVE-2026-34587 (opens in a new tab)How to fix?
Upgrade getkirby/cms to version 4.9.0, 5.4.0 or higher.
Overview
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements Used in a Template Engine via the Option::render() and Options::factory() code paths in the Option, Options, OptionsApi, and OptionsQuery classes. An attacker can inject template/query syntax into the text or info option fields by supplying crafted option data or by influencing API- or query-backed option sources, causing those expressions to be re-evaluated during rendering. This lets user-controlled content be interpreted as Kirby queries rather than treated as literal text, so rendered option labels can disclose unintended page data or other resolved content to the user.
Notes
- The vulnerable path is not limited to blueprint-defined static options: it also covers option lists built from
OptionsApiandOptionsQuery, which means attacker-controlled or editor-controlled source data can be reinterpreted when those providers are used in Panel fields such asselect,radio,tags,multiselect,checkboxes,color, andtoggles.
Workarounds
- If your site uses the
Optionspackage directly from plugin or site code, do not feed it untrusted query/API-backed option data until you can upgrade, because those sources can otherwise be rendered as executable Kirby queries.