Azrultech

**Name of the Vulnerable Software and Affected Versions** Kirby versions prior to 3.5.8 **Description** The issue concerns the writer field in Kirby, which stores formatted content as HTML code and does not escape HTML special characters against cross-site scripting (XSS) attacks. This allows malicious HTML code to be injected into the content file and executed in the browsers of site visitors and logged-in users. The vulnerability can be exploited by attackers who are in the group of authenticated Panel users, potentially leading to escalated privileges if they gain access to an admin user's Panel session. The estimated number of potentially affected devices is not specified. **Recommendations** For versions prior to 3.5.8, update to Kirby 3.5.8 or a later version to fix the vulnerability. As a temporary workaround, consider restricting access to the writer field for authenticated Panel users to minimize the risk of exploitation. If possible, avoid using the writer field until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Kirby versions prior to 3.5.8 **Description** The issue concerns Kirby's blocks field, which stores structured data for each block, and this data is used in block snippets to convert blocks to HTML for use in templates. The default snippet for the image block did not escape HTML special characters, making it possible to include malicious HTML code in the source, alt, and link fields of the image block. This code would then be displayed on the site frontend and executed in the browsers of site visitors and logged-in users. Attackers must be authenticated Panel users to exploit this weakness. The vulnerability allows for cross-site scripting (XSS) attacks, which can execute JavaScript code inside the site frontend or Panel session of other users. **Recommendations** For versions prior to 3.5.8, update to Kirby version 3.5.8 or a later version to fix the vulnerability. As a temporary workaround, consider escaping HTML special characters in the output from the default image block snippet or using a custom block snippet that either escapes the printed values or doesn't use them. Restrict access to the blocks field, especially the image block, to minimize the risk of exploitation. Avoid using the `source`, `alt`, and `link` fields in the image block until the issue is resolved.