NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #4129 most downloaded on Packagist
The Kirby core
Latest stable
5.6.3
Last release 17 days ago
05 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
297 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
translations root deprecated and will be removed in 3.3. Use i18n:translations instead
It's all about editing…
Working in teams has become a lot safer with our new content locking feature. Pages that are being edited are now automatically locked and other editors get informed about the editing user and cannot overwrite their ongoing changes.
You can now create conditional sections that are only shown when a field contains a specific value (i.e. a toggle is checked, a select field is at a certain option, etc.)
Conditional sections work exactly like conditional fields.
sections:
content:
type: fields
fields:
postType:
type: select
options:
- Gallery
- Image
gallery:
type: files
template: gallery-image
layout: cards
size: tiny
when:
postType: Gallery
image:
type: files
template: single-image
max: 1
layout: cards
when:
postType: Image
It's often easier to start a new page from existing content than to start from scratch. With the new "Duplicate" function you can now create new drafts from existing pages and decide to also copy files and even subpages.
You can now finally upload files directly in the files field.
You can now control each option for pages, files and users with fine-grained permissions:
options:
delete:
admin: true
editor: false
There's also a wildcard available to change the default for all roles:
options:
update:
*: false
editor: true
fields:
text:
label: Text
type: textarea
font: monospace
You can set any fraction and it will be automatically calculated into the right width.
fields:
mystructure:
label: Structure
type: structure
columns:
a:
width: 3/5
b:
width: 1/5
c:
width: 1/10
d:
width: 1/10
fields:
a:
label: A
type: text
b:
label: B
type: text
c:
label: C
type: text
d:
label: D
type: text
With the new "login" plugin type you can now swap Kirby's default login screen and add your own. This is perfect when you want to implement your own authentication methods.
Here's a quick example:
index.js
import LoginScreen from "./components/LoginScreen.vue";
panel.plugin('my/auth', {
login: LoginScreen
});
LoginScreen.vue
<template>
<form @submit.prevent="login">
<k-fieldset :fields="fields" @submit="login"></k-fieldset>
<k-button type="submit" icon="check">Authenticate</k-button>
</form>
</template>
<script>
export default {
computed: {
fields() {
return {
phone: {
placeholder: "+49 ",
label: "Phone",
type: "tel"
}
}
}
},
methods: {
login() {
/** Send 2FA auth link **/
}
}
};
</script>
Our slug generator now has language specific rules that improve the quality of created slugs drastically. You can combine this with custom rules for each language.
<?php
return [
'code' => 'de',
'default' => false,
'direction' => 'ltr',
'locale' => 'de_DE',
'name' => 'Deutsch',
'slug' => [
'ß' => 'sz'
]
];
<img width="479" alt="slugs" src="https://user-images.githubusercontent.com/24532/58875441-dca82180-86cb-11e9-9020-49b9dd0637a0.png">
For single-language setups you can define which ruleset to use in the config.php as well as define custom rules:
<?php
return [
'slugs' => 'de'
];
Str::$language = [
'ß' => 'sz'
];
Users and files can now have their own model classes – like pages. Model classes give you full access to extend and overwrite the functionalities of users and files based on their roles or templates.
class EditorUser extends User
{
// ...
}
class CoverFile extends File
{
// ...
}
Kirby::plugin('my/plugin', [
'fileModels' => [
'cover' => 'CoverFile'
],
'userModels' => [
'editor' => 'EditorUser'
],
'usersMethods' => [
'withArticles' => function () {
return $this->articles()->isNotEmpty();
}
]
]);
We drastically simplified routing in multi-language setups. You can now handle routes for a specific language or any language in a matter of seconds without writing redundant route definitions.
return [
'routes' => [
[
'pattern' => '(:any)',
'language' => 'en',
'action' => function ($language, $slug) {
if (page($slug)) {
return $this->next();
}
if ($page = page('notes/' . $slug)) {
return $page;
}
return false;
}
],
]
];
You can even add a page scope to the routes, which will automatically take care to handle translated slugs.
return [
'routes' => [
[
'pattern' => 'tag/(:any)',
'language' => '*',
'page' => 'notes',
'action' => function ($language, $page, $filter) {
return $page->render([
'filter' => $filter
]);
}
],
]
];
You can now define snippet alternatives if the first snippet cannot be found.
<?php snippet(['try/this', 'try/that', 'try/last']) ?>
This is perfect if you want to load a snippet based on a custom page field, but such a snippet might not always exist:
<?php snippet(['articles/' . $page->postType(), 'articles/default']) ?>
You can now use array syntax and nested queries in our query syntax.
// arrays
site.index.filterBy('template', 'in', ['note', 'album']);
// nested queries
kirby.collection("some-collection").not(kirby.collection("excluded-collection"))
The users field gets a lot more flexible with the addition of a query option. You can use this for example to filter users by role or any other custom field.
fields:
author:
label: Author
type: users
query: kirby.users.role("editor")
When you create mixins for blueprints, such as field definitions or entire tabs, you can now use them but unset definitions that you don't want/need.
# /site/blueprints/tabs/seo.yml
label: SEO
icon: search
fields:
seoTitle:
label: SEO Title
type: text
seoDescription:
label: SEO Description
type: text
Then in the extending blueprint …
tabs:
seo:
extends: tabs/seo
fields:
seoDescription: false
tt() helperNew tt() helper as shortcut for I18n::template()
// /site/languages/en.php
return [
'code' => 'en',
'default' => false,
'direction' => 'ltr',
'locale' => 'en_US',
'name' => 'English',
'translations' => [
'alert' => 'Attention: { message }'
]
];
In your templates …
<?= tt('alert', ['message' => 'Something is not right']) ?>
site.ymlYou can already control the preview URL for each page type in the page's blueprint, but in 3.2 you can now also set the same option in the site.yml
title: Site
preview: https://mycustomdomain.com
(image: myimage.jpg link: mydocument.pdf)download option for the file tag to avoid direct downloads: (file: myfile.pdf download: false)$field->toDate('d.m.Y', 'now') methodasset() method can now be used as preview images in the Panel$kirby->request()->domain() method$kirby->request()->path() method$page->images() collectionsroute:after hook can now manipulate the return valueMime::toExtensions() methodcreated plugin type for Panel plugins, which gives you full access to the Vue instance, the Vue router and VuexuploadFile.js helper to upload custom Blobs and pass the name properly in panel plugins.srcset for thumbs in lists and cards, so your browser can select the best resolution for you(Image: something.jpg) works as well as (image: something.jpg)tel: and mailto: linkshelp in sections gets translated correctly nowtranslations root deprecated and will be removed in 3.3. Use i18n:translations insteadFile::model() does no longer return the parent model. Use File::parent() insteadYour coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
KirbyText in the caption attribute of the (image:) tag now gets correctly converted
caption attribute of the (image:) tag now gets correctly converted->isLast()) on structure objectstranslate: false'smartypants' => trueNothing published for this version
Paginated structure fields open items correctly now
translate: false blueprint optionmin, an error dialog is shown.Languages::load() now reloads languages and returns them on repeated calls.Nothing published for this version
The image() helper uses the current $page if no path is specified
image() helper uses the current $page if no path is specified-0$page→previewUrl() can now handle query strings in blueprint definitions correctly$file→modified() returns the correct timestamp when the content has been modifiedmin requirement message in pages sections is fixedsvg() helper is now working reliably with OPcache and also avoids loading PHP codeNothing published for this version
This is a small patch release for an issue in multi-language setups. If the URL for the default language is set to /, switching languages became impos
This is a small patch release for an issue in multi-language setups. If the URL for the default language is set to /, switching languages became impossible. This release will fix that. We recommend this patch for all multi-language setups.
Single-language installations are not affected.
Request::ajax() is now marked as deprecated and should no longer be used
Only display fields in the Panel if their when option is fulfilled.
fields:
category:
label: Category
type: select
options:
a: A
b: B
c: C
other: Other …
other:
label: Enter your category
type: text
when:
category: other
This opens up a lot of new possibilities for Panel layouts:
Learn more about conditional fields …
You can now add images and other files to your textareas with the new file button and drag & drop uploads.
Define the button behavior with the files and uploads options:
textarea:
type: textarea
files: page.images
uploads: textarea-upload
Or fetch files from anywhere, upload them to specific pages and assign a specific template:
textarea:
type: textarea
files:
query: site.find("media").files.template("textarea-upload")
image:
cover: true
uploads:
parent: site.find("media")
template: textarea-upload
You can also deactivate file uploads:
textarea:
type: textarea
uploads: false
Learn more about the new file button …
The new $image->srcset() handles all the hard work of creating srcsets for responsive images and also takes care of resizing the different versions with our media API.
<img
src="<?= $image->url() ?>"
srcset="<?= $image->srcset([300, 800, 1024]) ?>"
alt="<?= $image->alt() ?>">
You can also modify the width definiton
$image->srcset([
800 => '1x',
1600 => '1.5x'
]);
To simplify srcset definitions across a site you can set them up in your config
<?php
return [
'thumbs' => [
'srcsets' => [
'default' => [300, 800, 1024],
'cover' => [800, 1024, 2048]
]
]
];
… and then use it in your templates …
// default
$image->srcset()
// particular preset
$image->srcset('cover')
You can now add help text to your sections to guide your editors with additional information.
sections:
gallery:
headline: Gallery
type: files
help: Images should have a ratio of about 3/2 to look best
<!-- image -->
You can now switch between the global page and user search to jump to the right place from anywhere in an instant.
The new global collections in v3 are a great way to keep your controllers and templates clean. Now you can organize them even better with nested collections. Create subfolders in /site/collections to group collection files and use them later like this …
$articles = collection('articles/latest');
We received a lot of requests to provide an additional method to parse KirbyText and Markdown without wrapping everything in <p> tags. There was even a plugin for v2, which solved this. We are happy that this feature has finally reached the core.
<p class="intro">
<?= $page->intro()->kirbyTextInline() ?>
</p>
To parse any kind of string, you can use the kirbyTextInline($string) helper. If you want to save some time while typing, you can use the $field->kti() and kti() shortcuts instead.
There are two new official API endpoints to search for pages and users:
GET /api/site/search?q=
GET /api/users/search?q=
panelUrl, panelImage, panelIcon, dragText)attachment icontranslate: false is no longer ignored in structure fieldssearch: false option for multiselect fieldslink tag no longer ignores non-default languages$field→kirbytext() or $field→kirbyText()$kirby→collection() now returns a clone of the collection to avoid global mutations.$item->toDate() on Structure objectsRequest::ajax() is now marked as deprecated and should no longer be used<template>
<k-upload @success="onSuccess" />
</template>
<script>
export default {
methods: {
onSuccess (uploads, response) {
// i.e.
response[0].type;
response[0].filename;
response[0].niceSize;
// etc.
}
}
}
</script>
Nothing published for this version
Update translations (cs, el, fa, ko)
rel attribute in HTML::a() will now overwrite predefined noopener and noreferrer values when a target is defined.title:
en: Client
de: Kunde
description:
en: The client can edit all pages
de: Der Kunde kann alle Seiten bearbeiten
<?php
return [
'thumbs' => [
'presets' => [
'default' => ['width' => 1024, 'quality' => 80],
'blurred' => ['blur' => true]
]
]
];
… and use them afterwards …
// default
$file->thumb()
// preset
$file->thumb('blurred')
empty option in all sections and fieldsempty option to users field and structure fieldPage::isUnlisted()'/'url set to '/'$this→next() handler in routes to jump to the next applicable route.return [
'routes' => [
[
'pattern' => '(:any)',
'action' => function ($slug) {
if ($page = page('photography')->find($slug)) {
return page($page);
}
$this->next();
}
]
]
];
Pages::find() now finds the right page even when you pass an extension in the path (i.e. page('blog/feed.json'))Nothing published for this version
Nothing published for this version
Nothing published for this version
Remove deprecated $kirby→root('emails')
UrlPreviewComponentsvg() helperCONTRIBUTING.md guideREADME.md to .github subfoldertemplates option$kirby→file() relative to other fileslanguage.created translation from sourceapi.allowInsecure option to disable the SSL requirement for API callsPage::modified() issues with custom date handler and no formatload() helperPage::isDescendantOf() with string argumentPage::update(), File::update(), User::update() and Site::update().asset() helperHtml::attr() method$kirby→root('emails')Field::model() method/ in the configNothing published for this version
Correctly load missing "empty" section mixin
Page::isChildOf method when used with page on first level(link: ) tag, in url() helper and Url::to() methodNothing published for this version
Drafts & custom publishing workflows
... and so much more. See what's new in v3!
This release fixes three path traversal vulnerabilities in the Kirby core:
This release fixes three path traversal vulnerabilities in the Kirby core:
| Description | Severity | CVE ID |
|---|---|---|
| Path traversal of snippet names during file system lookup | Medium (6.3) | CVE-2025-30159 |
| Path traversal of collection names during file system lookup | Medium (6.3) | CVE-2025-31493 |
| Path traversal in the router for PHP's built-in server | Low (2.3) | CVE-2025-30207 |
The first two vulnerabilities only affect Kirby sites that call the snippet() or collection() helpers with dynamic name values that could be controlled by an attacker. Sites that only use fixed calls to the snippet() or collection() helpers (i.e. calls with a simple string for the snippet/collection name) are not affected.
The last vulnerability only affects Kirby setups that use PHP's built-in server. Such setups are commonly only used during local development.
All three vulnerabilities have in common that they can be exploited via path traversal. By using special elements such as .. and / separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the ../ sequence, which in most modern operating systems is interpreted as the parent directory of the current location.
The missing path traversal checks allowed attackers to navigate and access all files on the server that were accessible to the PHP process, including files outside of the relevant system roots or even outside of the Kirby installation. Depending on the vulnerability, the existence of the traversed file could be revealed or contained PHP code could be executed.
You can read more about the vulnerabilities and their impact in the security advisories linked above.
Thanks to Bruno Meilick (@bnomei) and Tobias Möritz (@tobimori) for their responsible disclosure and for bringing this type of attack vector to our attention.
[!NOTE] If you deliberately use path traversal with the
snippet()helper in your projects, these uses will break after updating to this patched version. You can read more about this and possible alternatives in the security advisory.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users…
Severity: high (CVSS score 8.1)
Kirby's frontend and backend code did not enforce the existing languages.create and languages.delete permissions.
The missing permission checks allowed attackers with Panel access to manipulate the language definitions. The language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users.
If you have disabled the languages and/or api option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is not affected.
Thanks to Sebastian Eberlein of JUNO (@SebastianEberlein-JUNO) for reporting the identified issue.
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issues.
During our investigation of the security reports, we noticed that the documentation on the Markdown safe mode was inaccurate and incomplete.
The Markdown safe mode protects Markdown and KirbyText content from cross-site scripting (XSS) attacks. We have already documented the risk of raw HTML, however there are also risks in the Markdown syntax itself (e.g. malicious javascript: links). These risks are also mitigated by the safe mode. So we strongly recommend this mode for all Kirby sites that might have potential attackers in the group of authenticated Panel users.
The documentation on the safe mode contained a wrong code example that used an invalid safeMode option instead of the correct safe option. This has now been corrected. If you already use the safe mode, please check your code.
➡️ Read more
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.9.6) can now be customized with an option if needed: #5431
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.9.6) can now be customized with an option if needed: #5431
return [
'panel' => [
// allow frame embedding from the same domain
'frameAncestors' => true,
// allow frame embedding from the same *and* from the specified domains
'frameAncestors' => ['*.example.com', 'https://example.com'],
// allow frame embedding on any domain (not recommended)
'frameAncestors' => '*',
]
];
null #5428This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users…
Severity: high (CVSS score 8.1)
Kirby's frontend and backend code did not enforce the existing languages.create and languages.delete permissions.
The missing permission checks allowed attackers with Panel access to manipulate the language definitions. The language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users.
If you have disabled the languages and/or api option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is not affected.
Thanks to Sebastian Eberlein of JUNO (@SebastianEberlein-JUNO) for reporting the identified issue.
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issues.
During our investigation of the security reports, we noticed that the documentation on the Markdown safe mode was inaccurate and incomplete.
The Markdown safe mode protects Markdown and KirbyText content from cross-site scripting (XSS) attacks. We have already documented the risk of raw HTML, however there are also risks in the Markdown syntax itself (e.g. malicious javascript: links). These risks are also mitigated by the safe mode. So we strongly recommend this mode for all Kirby sites that might have potential attackers in the group of authenticated Panel users.
The documentation on the safe mode contained a wrong code example that used an invalid safeMode option instead of the correct safe option. This has now been corrected. If you already use the safe mode, please check your code.
➡️ Read more
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.8.4.1) can now be customized with an option if needed:
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.8.4.1) can now be customized with an option if needed:
return [
'panel' => [
// allow frame embedding from the same domain
'frameAncestors' => true,
// allow frame embedding from the same *and* from the specified domains
'frameAncestors' => ['*.example.com', 'https://example.com'],
// allow frame embedding on any domain (not recommended)
'frameAncestors' => '*',
]
];
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
Thanks to Shankar Acharya (@5hank4r), Alexandre Zanni (@noraj) at ACCEIS and Patrick Falb (@dapatrese) at FORMER 03 for responsibly reporting the identified issues.
.htaccessWe have updated the .htaccess that ships with our kits to the new version 2023-07-22, which adds protection against browser MIME type detection from malicious file uploads for files that have already been copied to the media folder. We recommend to update your sites’ .htaccess or server configuration with the new changes if you might have potential attackers in your group of authenticated Panel users or if your sites allow file uploads by visitors and the file extensions of uploaded files are not limited to a fixed safe list.
You can find the changes to the .htaccess in this commit and read more about the added rules in the security guide.
Thanks to Shankar Acharya (@5hank4r) for making us aware of this potential attack vector.
The Panel now sends the Content-Security-Policy: frame-ancestors 'none' header to increase the protection against clickjacking attacks. The session cookie was already set to SameSite before, so this is an additional layer of protection.
Thanks to Shankar Acharya (@5hank4r) for suggesting this security enhancement.
Xml data handler (e.g. Data::decode($string, 'xml')) and the Xml::parse() method no longer process XML external entities.Fixed potential content loss when auto-generating UUIDs. #4800
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users…
Severity: high (CVSS score 8.1)
Kirby's frontend and backend code did not enforce the existing languages.create and languages.delete permissions.
The missing permission checks allowed attackers with Panel access to manipulate the language definitions. The language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users.
If you have disabled the languages and/or api option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is not affected.
Thanks to Sebastian Eberlein of JUNO (@SebastianEberlein-JUNO) for reporting the identified issue.
Important note: This release marks the end of security support for Kirby 3.7. This version of Kirby has now reached its end of life and will no longer receive any updates whatsoever, including security updates. Please update to a more recent Kirby release to stay secure.
➡️ Read more
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issues.
During our investigation of the security reports, we noticed that the documentation on the Markdown safe mode was inaccurate and incomplete.
The Markdown safe mode protects Markdown and KirbyText content from cross-site scripting (XSS) attacks. We have already documented the risk of raw HTML, however there are also risks in the Markdown syntax itself (e.g. malicious javascript: links). These risks are also mitigated by the safe mode. So we strongly recommend this mode for all Kirby sites that might have potential attackers in the group of authenticated Panel users.
The documentation on the safe mode contained a wrong code example that used an invalid safeMode option instead of the correct safe option. This has now been corrected. If you already use the safe mode, please check your code.
➡️ Read more
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.7.5.2) can now be customized with an option if needed:
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.7.5.2) can now be customized with an option if needed:
return [
'panel' => [
// allow frame embedding from the same domain
'frameAncestors' => true,
// allow frame embedding from the same *and* from the specified domains
'frameAncestors' => ['*.example.com', 'https://example.com'],
// allow frame embedding on any domain (not recommended)
'frameAncestors' => '*',
]
];
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
Thanks to Shankar Acharya (@5hank4r), Alexandre Zanni (@noraj) at ACCEIS and Patrick Falb (@dapatrese) at FORMER 03 for responsibly reporting the identified issues.
.htaccessWe have updated the .htaccess that ships with our kits to the new version 2023-07-22, which adds protection against browser MIME type detection from malicious file uploads for files that have already been copied to the media folder. We recommend to update your sites’ .htaccess or server configuration with the new changes if you might have potential attackers in your group of authenticated Panel users or if your sites allow file uploads by visitors and the file extensions of uploaded files are not limited to a fixed safe list.
You can find the changes to the .htaccess in this commit and read more about the added rules in the security guide.
Thanks to Shankar Acharya (@5hank4r) for making us aware of this potential attack vector.
The Panel now sends the Content-Security-Policy: frame-ancestors 'none' header to increase the protection against clickjacking attacks. The session cookie was already set to SameSite before, so this is an additional layer of protection.
Thanks to Shankar Acharya (@5hank4r) for suggesting this security enhancement.
Xml data handler (e.g. Data::decode($string, 'xml')) and the Xml::parse() method no longer process XML external entities.This vulnerability allowed user enumeration, which is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby i…
Severity: medium (CVSS score 4.8)
Errors that occur during the processing of the code-based login and password reset were in some cases passed to the user. This includes errors of the code challenge itself (e.g. if the email could not be sent) and errors thrown inside the user.login:failed hook.
This vulnerability allowed user enumeration, which is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby installation. This information can be abused for social engineering attacks against users of the site or to find out the organizational structure of the company.
This vulnerability only affects you if you are using the code or password-reset auth method with the auth.methods option. It can only be successfully exploited under server configuration conditions outside of the attacker's control.
Thanks to Florian Merz (@florianmrz) of hatchery.io for responsibly reporting the identified issue.
Severity: medium (CVSS score 6.5)
We used the opportunity to review other parts of Kirby's authentication handling and found another part that is affected by a similar user enumeration vulnerability caused by a response discrepancy in Kirby's brute force protection system.
This vulnerability affects all Kirby sites with user accounts (unless Kirby's API and Panel are disabled in the config). It can only be exploited for targeted attacks because the attack does not scale to brute force.
This patch fixes an issue in the structure field. If you don't use the structure field in your application, you don't have to update.
This patch fixes an issue in the structure field. If you don't use the structure field in your application, you don't have to update.
Url::query() and $uri->query() no longer return empty results https://github.com/getkirby/kirby/issues/4446
Url::query() and $uri->query() no longer return empty results https://github.com/getkirby/kirby/issues/4446Image KirbyTag with caption doesn't trigger deprecation warning anymore #4435
uploads: false is set #4436This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users…
Severity: high (CVSS score 8.1)
Kirby's frontend and backend code did not enforce the existing languages.create and languages.delete permissions.
The missing permission checks allowed attackers with Panel access to manipulate the language definitions. The language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users.
If you have disabled the languages and/or api option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is not affected.
Thanks to Sebastian Eberlein of JUNO (@SebastianEberlein-JUNO) for reporting the identified issue.
Important note: This release marks the end of security support for Kirby 3.6. This version of Kirby has now reached its end of life and will no longer receive any updates whatsoever, including security updates. Please update to a more recent Kirby release to stay secure.
➡️ Read more
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issues.
During our investigation of the security reports, we noticed that the documentation on the Markdown safe mode was inaccurate and incomplete.
The Markdown safe mode protects Markdown and KirbyText content from cross-site scripting (XSS) attacks. We have already documented the risk of raw HTML, however there are also risks in the Markdown syntax itself (e.g. malicious javascript: links). These risks are also mitigated by the safe mode. So we strongly recommend this mode for all Kirby sites that might have potential attackers in the group of authenticated Panel users.
The documentation on the safe mode contained a wrong code example that used an invalid safeMode option instead of the correct safe option. This has now been corrected. If you already use the safe mode, please check your code.
➡️ Read more
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.6.6.3) can now be customized with an option if needed:
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.6.6.3) can now be customized with an option if needed:
return [
'panel' => [
// allow frame embedding from the same domain
'frameAncestors' => true,
// allow frame embedding from the same *and* from the specified domains
'frameAncestors' => ['*.example.com', 'https://example.com'],
// allow frame embedding on any domain (not recommended)
'frameAncestors' => '*',
]
];
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
Thanks to Shankar Acharya (@5hank4r), Alexandre Zanni (@noraj) at ACCEIS and Patrick Falb (@dapatrese) at FORMER 03 for responsibly reporting the identified issues.
.htaccessWe have updated the .htaccess that ships with our kits to the new version 2023-07-22, which adds protection against browser MIME type detection from malicious file uploads for files that have already been copied to the media folder. We recommend to update your sites’ .htaccess or server configuration with the new changes if you might have potential attackers in your group of authenticated Panel users or if your sites allow file uploads by visitors and the file extensions of uploaded files are not limited to a fixed safe list.
You can find the changes to the .htaccess in this commit and read more about the added rules in the security guide.
Thanks to Shankar Acharya (@5hank4r) for making us aware of this potential attack vector.
The Panel now sends the Content-Security-Policy: frame-ancestors 'none' header to increase the protection against clickjacking attacks. The session cookie was already set to SameSite before, so this is an additional layer of protection.
Thanks to Shankar Acharya (@5hank4r) for suggesting this security enhancement.
Xml data handler (e.g. Data::decode($string, 'xml')) and the Xml::parse() method no longer process XML external entities.This vulnerability allowed user enumeration, which is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby i…
Severity: medium (CVSS score 4.8)
Errors that occur during the processing of the code-based login and password reset were in some cases passed to the user. This includes errors of the code challenge itself (e.g. if the email could not be sent) and errors thrown inside the user.login:failed hook.
This vulnerability allowed user enumeration, which is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby installation. This information can be abused for social engineering attacks against users of the site or to find out the organizational structure of the company.
This vulnerability only affects you if you are using the code or password-reset auth method with the auth.methods option. It can only be successfully exploited under server configuration conditions outside of the attacker's control.
Thanks to Florian Merz (@florianmrz) of hatchery.io for responsibly reporting the identified issue.
Severity: medium (CVSS score 6.5)
We used the opportunity to review other parts of Kirby's authentication handling and found another part that is affected by a similar user enumeration vulnerability caused by a response discrepancy in Kirby's brute force protection system.
This vulnerability affects all Kirby sites with user accounts (unless Kirby's API and Panel are disabled in the config). It can only be exploited for targeted attacks because the attack does not scale to brute force.
You are also *not* affected by these vulnerabilities if your site doesn't have untrustworthy users with Panel access or a way to modify field values f…
Severity: high (CVSS score 7.1)
The tags and multiselect fields allow to select tags from an autocompleted list. The tags field also allows to enter new tags or edit existing tags. Kirby already handled escaping of the autocompleted tags, but unfortunately the Panel used HTML rendering for new or edited tags as well as for custom tags from the content file.
This allowed attackers with Panel access to store malicious HTML code in a tag. The browser of the victim who visited the modified page in the Panel will then have rendered this malicious HTML code.
It also allowed self-inflicted XSS attacks in the tags field (meaning that malicious code is executed in the browser of the user who entered it). This could be used in social engineering attacks where a victim is convinced by an attacker to enter malicious code into a tags field.
Visitors without Panel access could only use this attack vector if your site allows changing the content of a tags or multiselect field from a frontend form (for example user self-registration or the creation of pages from a contact or other frontend form). If you validate or sanitize the provided form data, you are already protected against such attacks by external visitors.
You are also not affected by these vulnerabilities if your site doesn't have untrustworthy users with Panel access or a way to modify field values from the frontend or if you don't use the tags or multiselect fields.
Note: The fixes for these vulnerabilities have the side effect that values in the tags and multiselect fields that come from dynamic options are displayed with double escaping (e.g. the & character is displayed as &). We will fix the double escaping issues with a refactoring of the options fields (tags, multiselect, checkboxes, radio, select and toggles) in Kirby 3.8.
This release is a patch release for 3.6.3. We introduced a regression that broke parameters in URLs. I.e. https://example.com/blog/page:2 and thus als
This release is a patch release for 3.6.3. We introduced a regression that broke parameters in URLs. I.e. https://example.com/blog/page:2 and thus also pagination and all kinds of URL filters based on such parameters.
PHP 8.1: Fix more arguments of built-in functions https://github.com/getkirby/kirby/pull/4023
phpmailer https://github.com/getkirby/kirby/pull/4021claviska/simpleimage https://github.com/getkirby/kirby/pull/4008plugins.js regression https://github.com/getkirby/kirby/issues/1062The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.5.8.3) can now be customized with an option if needed:
The Content-Security-Policy: frame-ancestors header sent by the Panel (introduced in 3.5.8.3) can now be customized with an option if needed:
return [
'panel' => [
// allow frame embedding from the same domain
'frameAncestors' => true,
// allow frame embedding from the same *and* from the specified domains
'frameAncestors' => ['*.example.com', 'https://example.com'],
// allow frame embedding on any domain (not recommended)
'frameAncestors' => '*',
]
];
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
This release fixes several vulnerabilities that were all responsibly reported to us in June 2023:
Thanks to Shankar Acharya (@5hank4r), Alexandre Zanni (@noraj) at ACCEIS and Patrick Falb (@dapatrese) at FORMER 03 for responsibly reporting the identified issues.
.htaccessWe have updated the .htaccess that ships with our kits to the new version 2023-07-22, which adds protection against browser MIME type detection from malicious file uploads for files that have already been copied to the media folder. We recommend to update your sites’ .htaccess or server configuration with the new changes if you might have potential attackers in your group of authenticated Panel users or if your sites allow file uploads by visitors and the file extensions of uploaded files are not limited to a fixed safe list.
You can find the changes to the .htaccess in this commit and read more about the added rules in the security guide.
Thanks to Shankar Acharya (@5hank4r) for making us aware of this potential attack vector.
The Panel now sends the Content-Security-Policy: frame-ancestors 'none' header to increase the protection against clickjacking attacks. The session cookie was already set to SameSite before, so this is an additional layer of protection.
Thanks to Shankar Acharya (@5hank4r) for suggesting this security enhancement.
Xml data handler (e.g. Data::decode($string, 'xml')) and the Xml::parse() method no longer process XML external entities.This vulnerability allowed user enumeration, which is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby i…
Severity: medium (CVSS score 4.8)
Errors that occur during the processing of the code-based login and password reset were in some cases passed to the user. This includes errors of the code challenge itself (e.g. if the email could not be sent) and errors thrown inside the user.login:failed hook.
This vulnerability allowed user enumeration, which is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby installation. This information can be abused for social engineering attacks against users of the site or to find out the organizational structure of the company.
This vulnerability only affects you if you are using the code or password-reset auth method with the auth.methods option. It can only be successfully exploited under server configuration conditions outside of the attacker's control.
Thanks to Florian Merz (@florianmrz) of hatchery.io for responsibly reporting the identified issue.
Severity: medium (CVSS score 6.5)
We used the opportunity to review other parts of Kirby's authentication handling and found another part that is affected by a similar user enumeration vulnerability caused by a response discrepancy in Kirby's brute force protection system.
This vulnerability affects all Kirby sites with user accounts (unless Kirby's API and Panel are disabled in the config). It can only be exploited for targeted attacks because the attack does not scale to brute force.
You are also *not* affected by these vulnerabilities if your site doesn't have untrustworthy users with Panel access or a way to modify field values f…
Severity: high (CVSS score 7.1)
The tags and multiselect fields allow to select tags from an autocompleted list. The tags field also allows to enter new tags or edit existing tags. Kirby already handled escaping of the autocompleted tags, but unfortunately the Panel used HTML rendering for new or edited tags as well as for custom tags from the content file.
This allowed attackers with Panel access to store malicious HTML code in a tag. The browser of the victim who visited the modified page in the Panel will then have rendered this malicious HTML code.
It also allowed self-inflicted XSS attacks in the tags field (meaning that malicious code is executed in the browser of the user who entered it). This could be used in social engineering attacks where a victim is convinced by an attacker to enter malicious code into a tags field.
Visitors without Panel access could only use this attack vector if your site allows changing the content of a tags or multiselect field from a frontend form (for example user self-registration or the creation of pages from a contact or other frontend form). If you validate or sanitize the provided form data, you are already protected against such attacks by external visitors.
You are also not affected by these vulnerabilities if your site doesn't have untrustworthy users with Panel access or a way to modify field values from the frontend or if you don't use the tags or multiselect fields.
Note: The fixes for these vulnerabilities have the side effect that every value in the tags and multiselect fields is displayed with double escaping (e.g. the & character is displayed as &) when dynamic options are enabled, while dynamic options themselves are displayed with triple escaping. We will fix the double/triple escaping issues with a refactoring of the options fields (tags, multiselect, checkboxes, radio, select and toggles) in Kirby 3.8.
Severity: medium (CVSS score 5.9)
The multiselect field allows to select tags from an autocompleted list. Unfortunately, the Panel in Kirby 3.5 used HTML rendering for the raw option value.
This allowed attackers with influence on the options source (e.g. content of sibling pages or an API endpoint) to inject HTML code. If a page in the Panel that uses the manipulated multiselect options was visited by a victim and the victim opened the autocomplete dropdown, the victim's browser will then have rendered this malicious HTML code.
You are not affected by this vulnerability if you don't use the multiselect field or only use it with options that cannot be manipulated by attackers.
This is a patch release for a regression in 3.5.7. The regression in 3.5.7 was causing an error in templates when the layout field was empty and the -
This is a patch release for a regression in 3.5.7. The regression in 3.5.7 was causing an error in templates when the layout field was empty and the ->toLayouts() method was called. If you are not using the layout field, you don't necessarily have to update to this patch release.
->toLayouts() method on an empty layout field #3482$collection->filterBy() methodFix regression in go() helper without args #3160
go() helper without args #3160This release fixes three path traversal vulnerabilities in the Kirby core:
This release fixes three path traversal vulnerabilities in the Kirby core:
| Description | Severity | CVE ID |
|---|---|---|
| Path traversal of snippet names during file system lookup | Medium (6.3) | CVE-2025-30159 |
| Path traversal of collection names during file system lookup | Medium (6.3) | CVE-2025-31493 |
| Path traversal in the router for PHP's built-in server | Low (2.3) | CVE-2025-30207 |
The first two vulnerabilities only affect Kirby sites that call the snippet() or collection() helpers with dynamic name values that could be controlled by an attacker. Sites that only use fixed calls to the snippet() or collection() helpers (i.e. calls with a simple string for the snippet/collection name) are not affected.
The last vulnerability only affects Kirby setups that use PHP's built-in server. Such setups are commonly only used during local development.
All three vulnerabilities have in common that they can be exploited via path traversal. By using special elements such as .. and / separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the ../ sequence, which in most modern operating systems is interpreted as the parent directory of the current location.
The missing path traversal checks allowed attackers to navigate and access all files on the server that were accessible to the PHP process, including files outside of the relevant system roots or even outside of the Kirby installation. Depending on the vulnerability, the existence of the traversed file could be revealed or contained PHP code could be executed.
You can read more about the vulnerabilities and their impact in the security advisories linked above.
Thanks to Bruno Meilick (@bnomei) and Tobias Möritz (@tobimori) for their responsible disclosure and for bringing this type of attack vector to our attention.
[!NOTE] If you deliberately use path traversal with the
snippet()helper in your projects, these uses will break after updating to this patched version. You can read more about this and possible alternatives in the security advisory.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users…
Severity: high (CVSS score 8.1)
Kirby's frontend and backend code did not enforce the existing languages.create and languages.delete permissions.
The missing permission checks allowed attackers with Panel access to manipulate the language definitions. The language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage.
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users.
If you have disabled the languages and/or api option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is not affected.
Thanks to Sebastian Eberlein of JUNO (@SebastianEberlein-JUNO) for reporting the identified issue.
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
This release fixes several vulnerabilities that were all responsibly reported to us in February 2024:
Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issues.
During our investigation of the security reports, we noticed that the documentation on the Markdown safe mode was inaccurate and incomplete.
The Markdown safe mode protects Markdown and KirbyText content from cross-site scripting (XSS) attacks. We have already documented the risk of raw HTML, however there are also risks in the Markdown syntax itself (e.g. malicious javascript: links). These risks are also mitigated by the safe mode. So we strongly recommend this mode for all Kirby sites that might have potential attackers in the group of authenticated Panel users.
The documentation on the safe mode contained a wrong code example that used an invalid safeMode option instead of the correct safe option. This has now been corrected. If you already use the safe mode, please check your code.
➡️ Read more
One column per quarter.