Advisory record · GHSA-xrvh-rvc4-5m43

Kirby vulnerable to unrestricted file upload of user avatar images

CVSS 4.6 MediumEPSS 0.0097 · 62nd percentile

Published by the GitHub Advisory Database at 26 Feb 2024, 16:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
getkirby/cmsPackagist<3.6.6.5 || >=3.7.0, <3.7.5.4 || >=3.8.0, <3.8.4.3 || >=3.9.0, <3.9.8.1 || >=3.10.0, <3.10.0.1 || >=4.0.0, <4.1.13.6.6.5, 3.7.5.4, 3.8.4.3, 3.9.8.1, 3.10.0.1, 4.1.1
Identifiers
GHSA-xrvh-rvc4-5m43 · CVE-2024-26483 · PKSA-yxtp-sp4n-y3tf
Weakness (CWE)
CWE-79 · CWE-94
Published
26 Feb 2024
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Kirby CMS (getkirby/cms) versions before 3.6.6.5, from 3.7.0 before 3.7.5.4, from 3.8.0 before 3.8.4.3, from 3.9.0 before 3.9.8.1, from 3.10.0 before 3.10.0.1, and from 4.0.0 before 4.1.1 do not validate the file type of user avatar uploads. An authenticated Panel user can upload non-image files as their avatar, and a user or visitor must interact with the file for an attack, such as cross-site scripting, to occur. Upgrade to 3.6.6.5, 3.7.5.4, 3.8.4.3, 3.9.8.1, 3.10.0.1, 4.1.1, or a later version. The source gives no workaround.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.6 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0097, the 62nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:25 UTC First seen by agentprime
  2. 31 Oct 2026, 14:25 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.