https://feed.craftedsignal.io/products/cms--5.0.0--5.4.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 26 May 2026 23:52:40 +0000https://feed.craftedsignal.io/briefs/2026-05-kirby-cms-method-call/Tue, 26 May 2026 23:52:40 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-kirby-cms-method-call/Kirby CMS is vulnerable to arbitrary method call via REST API search and collection query endpoints, allowing attackers to execute sensitive methods like password disclosure or privilege escalation, patched in versions 4.9.1 and 5.4.1.Kirby CMS versions before 4.9.1 and versions 5.0.0 through 5.4.0 are susceptible to an arbitrary method call vulnerability via its REST API. The vulnerability stems from insufficient validation of model attributes used in collection queries. An authenticated attacker with access to the Panel can exploit this to invoke arbitrary model methods, potentially leading to sensitive data disclosure (e.g., password hashes, filesystem paths) or unauthorized actions like privilege escalation or data deletion. This issue affects all Kirby sites where potential attackers are authenticated Panel users. The vulnerability was reported responsibly and has been addressed in Kirby versions 4.9.1 and 5.4.1.

Attack Chain

1. An attacker authenticates to the Kirby Panel.
2. The attacker crafts a malicious REST API request targeting a collection endpoint such as /site/children or /users.
3. The attacker includes a collection query parameter (e.g., filter, sort) with an arbitrary model method as the attribute.
4. The vulnerable Kirby CMS endpoint processes the request without proper validation of the model attribute.
5. The specified model method is executed, potentially disclosing sensitive information like password hashes via password() or filesystem paths via root().
6. Alternatively, the attacker could trigger impactful actions like privilege escalation by calling loginPasswordless() or data deletion by calling delete().
7. The attacker gains unauthorized access or causes data loss, depending on the method called and the attacker’s permissions.

Impact

Successful exploitation of this vulnerability allows attackers to disclose sensitive information or perform unauthorized actions. This can lead to complete compromise of the Kirby CMS instance, including unauthorized access to content, modification of data, or denial of service. The impact is high, affecting all Kirby sites with authenticated Panel users, leading to privilege escalation or data loss, depending on the permissions of the authenticated user.

Recommendation

• Upgrade to Kirby CMS version 4.9.1, 5.4.1, or later to patch CVE-2026-44174.
• Implement input validation on REST API endpoints to prevent arbitrary method calls.
• Monitor web server logs for suspicious API requests containing potentially malicious method calls in query parameters.
• Deploy the Sigma rules in this brief to your SIEM and tune for your environment.

]]>highthreatarbitrary-code-executionprivilege-escalationweb-applicationhttps://feed.craftedsignal.io/briefs/2026-05-kirby-cms-xss/Tue, 26 May 2026 23:52:25 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-kirby-cms-xss/Kirby CMS is vulnerable to cross-site scripting (XSS) via the list field or list block, allowing an authenticated Panel user with update permission to inject malicious HTML code into the content file, which is then executed in the browsers of site visitors and logged-in users; the vulnerability is tracked as CVE-2026-44175 and has been patched in versions 4.9.1 and 5.4.1.Kirby CMS versions prior to 4.9.1 and from 5.0.0 to 5.4.0 are susceptible to a stored cross-site scripting (XSS) vulnerability, identified as CVE-2026-44175, stemming from the improper sanitization of list field content. This vulnerability affects all Kirby sites that use the list field or list block when content is authored by users who may not be fully trusted. An attacker requires an authenticated Panel user with update permission to any list field or list block. The attack surfaces in the site frontend, not the Panel itself. Kirby sites are not affected if they don’t use the list field (or blocks field with the list block) in any of their blueprints, or if every user who can edit content is fully trusted.

Attack Chain

1. An attacker gains authenticated access to the Kirby Panel with update permissions.
2. The attacker identifies a page or content structure that utilizes a ’list’ field or ‘blocks’ field with the ’list’ block.
3. The attacker crafts a malicious payload containing JavaScript code embedded within HTML tags.
4. The attacker injects the malicious payload into the ’list’ field content, either directly via API or through the Panel’s editing interface.
5. The attacker saves the modified content. The injected payload is stored within the content files on the server.
6. A user (either another authenticated user or an unauthenticated visitor) requests the page containing the affected ’list’ field on the site frontend.
7. The server renders the page, including the injected malicious HTML code from the ’list’ field.
8. The user’s browser executes the injected JavaScript code, potentially leading to session hijacking, data theft, or other malicious actions.

Impact

Successful exploitation of this XSS vulnerability (CVE-2026-44175) allows an attacker to execute arbitrary JavaScript code in the context of a user’s browser session. This can lead to credential theft, session hijacking, defacement of the website, or redirection to malicious sites. The impact is high severity, as it affects all Kirby sites using the list field when content is authored by users who may not be fully trusted. The number of victims depends on the number of affected sites and the frequency with which users access pages containing the injected payload.

Recommendation

• Upgrade to Kirby CMS version 4.9.1 or 5.4.1 or later to apply the patch that sanitizes list field content, mitigating the XSS vulnerability (CVE-2026-44175).
• Implement strict input validation and output encoding mechanisms on all user-supplied data within the Kirby CMS environment.
• Review existing content for potentially malicious code within list fields and sanitize the content.
• Deploy a Web Application Firewall (WAF) with rules to detect and block XSS attacks targeting Kirby CMS, specifically focusing on the ’list’ field and ‘blocks’ field inputs.
• Enable logging for all API requests to the Kirby Panel to monitor for suspicious activity and potential payload injections.

]]>highthreatxssCVE-2026-44175kirby-cmsweb-application