HTML Injection Vulnerability in Kirby CMS
Summary
CVE-2024-26482: Withdrawn Advisory: Kirby CMS HTML injection vulnerability. Affects getkirby/cms versions < 4.1.0. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Kirby CMS is a popular content management system that allows users to create and manage websites with ease. It provides a flexible and intuitive interface for content editing and layout customization. However, a vulnerability has been discovered in the Edit Content Layout module of Kirby CMS version 4.1.0.
Vulnerability Detail
The vulnerability is an HTML injection issue that allows attackers to execute arbitrary code by injecting a crafted payload. This can lead to various security risks, including unauthorized access, data manipulation, and remote code execution. The vulnerability affects all versions of Kirby CMS up to and including 4.1.0.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no known workaround for this vulnerability. It is crucial to apply the official patch or upgrade to a fixed version of Kirby CMS to mitigate the risk.
Conclusion
The HTML injection vulnerability in Kirby CMS version 4.1.0 poses a significant security risk. It is crucial for users to upgrade to a patched version or apply the official fix to mitigate the risk of arbitrary code execution. For further support and guidance, please reach out to DevNack.com.
See every vulnerability recorded for getkirby/cms →
FAQ
The vulnerability allows attackers to execute arbitrary code, potentially leading to unauthorized access, data manipulation, and remote code execution.
All versions of Kirby CMS up to and including 4.1.0 are affected by this vulnerability.
No, there is no known workaround. It is essential to apply the official patch or upgrade to a fixed version of Kirby CMS.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. It analyzes your composer.lock file and provides real-time alerts for open-source vulnerabilities.
For further support and assistance in vulnerability remediation, you can contact info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for getkirby/cms.
