CVE-2024-26482: High severity getkirby Kirby vulnerability

Published Feb 22, 2024
·
Updated

Withdrawn Advisory This advisory has been withdrawn because the vendor reports that some HTML formatting (such as with an H1 element) is allowed, but there is backend sanitization such that the reporter's mentioned "injecting malicious scripts" would not occur.

Original Advisory An HTML injection vulnerability in the Edit Content Layout module of Kirby CMS v4.1.0 allows attackers to execute arbitrary code via a crafted payload.

Other sources

An HTML injection vulnerability exists in the Edit Content Layout module of Kirby CMS v4.1.0. NOTE: the vendor disputes the significance of this report because some HTML formatting (such as with an H1 element) is allowed, but there is backend sanitization such that the reporter's mentioned "injecting malicious scripts" would not occur.

MITRE

Affected Software

2 affected components
composer/getkirby/cms<=4.1.0
getkirby Kirby=4.1.0

Event History

Feb 22, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·05:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 AM
Affected Software
Advisory Published
via GitHub·06:30 AM
Aug 30, 2024
Withdrawn
via GitHub·02:42 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-26482?

The severity of CVE-2024-26482 has been mitigated due to backend sanitization of HTML input as reported by the vendor.

2

Which versions of software are affected by CVE-2024-26482?

CVE-2024-26482 affects versions of Kirby CMS up to and including 4.1.0.

3

How do I fix CVE-2024-26482?

There is no fix required for CVE-2024-26482 since the vulnerability has been mitigated by the vendor's backend sanitization.

4

Can CVE-2024-26482 be exploited?

No, CVE-2024-26482 cannot be exploited due to the implemented backend sanitization that prevents script injection.

5

Is there a workaround for CVE-2024-26482?

No specific workaround for CVE-2024-26482 is necessary as the vulnerability has been resolved by vendor updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203