Vulnerability Database · Packagist · getkirby/cms · Version

getkirby/cms 4.6.1

4.6.1 is affected by 27 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 12 Medium 14 Low 0 Unrated 0

Database updated 23/Oct/2026

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

getkirby/cms 4.6.1 vulnerabilities

27 vulnerabilities cover getkirby/cms 4.6.1. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2026-54003: Kirby CMS Critical Vulnerability in External Initialization of the Panel 9.1 critical 4.9.4 18 Jun 2026
CVE-2026-44174: Kirby CMS Arbitrary Method Call Vulnerability via REST API 8.7 high 4.9.1 26 May 2026
CVE-2026-54002: Kirby CMS Cross-Site Scripting (XSS) Vulnerability Due to Incomplete HTML/XML Sanitization 8.5 high 4.9.4 18 Jun 2026
CVE-2026-44175: Kirby CMS List Field XSS Vulnerability 8.5 high 4.9.1 26 May 2026
CVE-2026-45368: Kirby CMS Cross-Site Scripting (XSS) Vulnerability in KirbyTags and Image Blocks 8.4 high 4.9.1 27 May 2026
CVE-2026-75594: Kirby CMS Path Traversal Vulnerability in Media Handling 8.2 high 4.9.5 31 Aug 2026
CVE-2026-34587: Kirby CMS Server-Side Template Injection Vulnerability 7.6 high 4.9.0 23 Apr 2026
CVE-2026-49276: Kirby CMS Self-XSS Vulnerability in Writer Field 7.4 high 4.9.4 18 Jun 2026
CVE-2026-54005: Kirby CMS Pages Access Bypass in REST API 7.1 high 4.9.4 18 Jun 2026
CVE-2026-42069: Kirby CMS Insufficient Permission Controls Allow Unauthorized Access 7.1 high 4.9.0 04 May 2026
CVE-2026-42137: Kirby CMS Insufficient Permission Checks in Panel and REST API 7.1 high 4.9.0 30 Apr 2026
CVE-2026-41325: Kirby CMS Authorization Bypass Vulnerability 7.1 high 4.9.0 24 Apr 2026
HTML Injection Vulnerability in Kirby CMS 7.1 high No fix published 22 Feb 2024
CVE-2026-75592: Kirby CMS Path Traversal Vulnerability in Media Handling 6.9 medium 4.9.5 02 Sep 2026
CVE-2026-69127: Kirby CMS REST API Path Exposure Vulnerability 6.9 medium 4.9.5 01 Sep 2026
CVE-2026-50188: Kirby CMS HTTP Header Injection Vulnerability 6.9 medium 4.9.4 18 Jun 2026
CVE-2026-32870: XML Injection Vulnerability in getkirby/cms 6.9 medium 4.9.0 23 Apr 2026
CVE-2026-29905: Kirby CMS Persistent DoS via Malformed Image Upload 6.5 medium 5.2.0-rc.1 27 Mar 2026
CVE-2026-54004: Kirby CMS - Unauthorized Access to Top-Level Draft Files 6.3 medium 4.9.4 18 Jun 2026
CVE-2026-44176: Kirby CMS Pages Access Vulnerability Allows Unauthorized Draft Access 6.0 medium 4.9.1 26 May 2026
CVE-2018-14520: Kirby CMS 2.5.12 Cross-site Scripting 5.4 medium No fix published 25 Aug 2022
CVE-2026-49274: Kirby CMS Pages Access Vulnerability 5.3 medium 4.9.4 18 Jun 2026
CVE-2026-45334: Kirby CMS Content Lock Vulnerability Exposes User IDs and Emails 5.3 medium 4.9.1 27 May 2026
CVE-2026-42051: Kirby CMS Version and License Data Exposure to Authenticated Users 5.3 medium 4.9.0 04 May 2026
CVE-2026-42174: Kirby CMS User Avatar Permission Bypass Vulnerability 5.3 medium 4.9.0 04 May 2026
CVE-2026-40099: Kirby CMS Page Creation API Bypass Vulnerability 5.3 medium 4.9.0 23 Apr 2026
CVE-2018-14519: Kirby CMS 2.5.12 Cross-site Request Forgery 4.3 medium No fix published 25 Aug 2022

Looking for another version, or everything Vulert holds for getkirby/cms?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About getkirby/cms 4.6.1

Is getkirby/cms 4.6.1 vulnerable?

Yes. 27 vulnerabilities in the Vulert database cover getkirby/cms 4.6.1: 1 critical, 12 high, 14 medium and 0 low. Each entry above names the fixed version to move to.

How do I monitor getkirby/cms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the getkirby/cms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.