CVE-2024-26483: XSS

Published Feb 22, 2024
·
Updated

TL;DR

This vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users.

The attack requires user interaction by another user or visitor and cannot be automated.

----

Introduction

Unrestricted upload of files with a dangerous type is a type of vulnerability that allows to circumvent expectations and protections in the server setup or backend code. Uploaded files are not checked for their compliance with the intended purpose of the upload target, which can introduce secondary attack vectors.

While the vulnerability described here does not allow critical attacks like remote code execution (RCE), it can still be abused to upload unexpected file types that could for example make it possible to perform cross-site scripting (XSS) attacks.

Impact

Users with Panel access can upload a user avatar in their own account view. This avatar is intended to be an image, however the file type or file extension was not validated on the backend. This effectively allowed to upload many types of files that would then be stored with the filename profile and the provided file extension.

While the upload is protected against dangerous file types such as HTML files or executable PHP files, this could be abused to upload unexpected files such as PDFs that would then be available via a direct link. These links could be shared to other users.

Patches

The problem has been patched in Kirby 3.6.6.5, Kirby 3.7.5.4, Kirby 3.8.4.3, Kirby 3.9.8.1, Kirby 3.10.0.1, and Kirby 4.1.1. Please update to one of these or a later version to fix the vulnerability.

In all of the mentioned releases, we have added validations that prevent any files that don't have an image file extension or MIME type from being uploaded as a user avatar.

Credits

Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issue.

Other sources

An arbitrary file upload vulnerability in the Profile Image module of Kirby CMS v4.1.0 allows attackers to execute arbitrary code via a crafted PDF file.

MITRE

Affected Software

12 affected componentsFixes available
composer/getkirby/cms>=4.0.0<=4.1.0
4.1.1
composer/getkirby/cms=3.10.0
3.10.0.1
composer/getkirby/cms>=3.9.0<=3.9.8
3.9.8.1
composer/getkirby/cms>=3.8.0<=3.8.4.2
3.8.4.3
composer/getkirby/cms>=3.7.0<=3.7.5.3
3.7.5.4
composer/getkirby/cms<=3.6.6.4
3.6.6.5
getkirby Kirby<3.6.6.5
getkirby Kirby>=3.7.0<3.7.5.4
getkirby Kirby>=3.8.0<3.8.4.3
getkirby Kirby>=3.9.0<3.9.8.1
getkirby Kirby>=4.0.0<=4.1.1
getkirby Kirby=3.10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/getkirby/cms to a version that resolves this vulnerability.

    Fixed in 4.1.1
  2. Upgrade

    Upgrade composer/getkirby/cms to a version that resolves this vulnerability.

    Fixed in 3.10.0.1
  3. Upgrade

    Upgrade composer/getkirby/cms to a version that resolves this vulnerability.

    Fixed in 3.9.8.1
  4. Upgrade

    Upgrade composer/getkirby/cms to a version that resolves this vulnerability.

    Fixed in 3.8.4.3
  5. Upgrade

    Upgrade composer/getkirby/cms to a version that resolves this vulnerability.

    Fixed in 3.7.5.4
  6. Upgrade

    Upgrade composer/getkirby/cms to a version that resolves this vulnerability.

    Fixed in 3.6.6.5
  7. Upgrade

    Upgrade Kirby CMS to a version that resolves this vulnerability.

    Fixed in 3.6.6.5
  8. Upgrade

    Upgrade Kirby CMS to a version that resolves this vulnerability.

    Fixed in 3.7.5.4
  9. Upgrade

    Upgrade Kirby CMS to a version that resolves this vulnerability.

    Fixed in 3.8.4.3
  10. Upgrade

    Upgrade Kirby CMS to a version that resolves this vulnerability.

    Fixed in 3.9.8.1
  11. Upgrade

    Upgrade Kirby CMS to a version that resolves this vulnerability.

    Fixed in 3.10.0.1
  12. Upgrade

    Upgrade Kirby CMS to a version that resolves this vulnerability.

    Fixed in 4.1.1

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
Description
Data Sourced
via NVD·05:15 AM
SeverityWeaknessAffected Software
Feb 26, 2024
Advisory Published
via GitHub·04:22 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-26483?

CVE-2024-26483 is considered a high-severity vulnerability due to its potential for unauthorized file uploads by authenticated users.

2

How do I fix CVE-2024-26483?

To address CVE-2024-26483, update your Kirby CMS installation to versions 4.1.1, 3.10.0.1, 3.9.8.1, 3.8.4.3, 3.7.5.4, or 3.6.6.5 as applicable.

3

Who is affected by CVE-2024-26483?

CVE-2024-26483 affects all users of Kirby CMS versions prior to the specified patched versions where authenticated Panel users may upload dangerous files.

4

Can CVE-2024-26483 be exploited remotely?

CVE-2024-26483 cannot be exploited automatically and requires user interaction, making it reliant on the actions of another authenticated user.

5

What type of vulnerability is CVE-2024-26483?

CVE-2024-26483 is classified as an unrestricted file upload vulnerability, allowing potentially harmful files to be uploaded to the server.

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