Skip to main content
VulnerabilityPublished

CVE-2026-54004: getkirby kirby · Missing Authorization

Affects getkirby kirbySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 5.4.4 or 4.9.4 when convenient.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.4.4, 4.9.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade kirby and getkirby/kirby to 5.4.4 or 4.9.4.

Affected software

ProductAffectedFixed in
getkirbykirbyAffected
  • >=5.0.0 <5.4.4
Fixed in
  • 5.4.4
getkirbykirbyAffected
  • <4.9.4
Fixed in
  • 4.9.4
GitHubgetkirby/kirbypkg:github/getkirby/kirbyOther threatsAffected
  • <4.9.4
  • <5.4.4
Fixed in
  • 4.9.4
  • 5.4.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Kirby CMS to version 4.9.4 or later, or 5.4.4 or later, where this authorization issue has been fixed. No other mitigation or temporary workaround is documented. Patch status is confirmed fixed in these versions.

Description

Kirby is an open-source content management system. Prior to 4.9.4 and 5.4.4, Kirby sites with content.fileRedirects enabled could redirect unauthenticated clean file URL requests for files stored in top-level draft pages to physical media URLs without checking page access permissions or preview tokens, leading to disclosure of draft file contents. This issue is fixed in versions 4.9.4 and 5.4.4.

References

Community reviews

Loading reviews…