How severe is GHSA-2h7v-4372-f6x2?

No CVSS score has been assigned to GHSA-2h7v-4372-f6x2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2h7v-4372-f6x2?

GHSA-2h7v-4372-f6x2 affects the following packages: getkirby/cms (Packagist), getkirby/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2h7v-4372-f6x2?

Update getkirby/cms to 4.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2h7v-4372-f6x2 is resolved across your whole dependency graph.

How do I detect GHSA-2h7v-4372-f6x2 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2h7v-4372-f6x2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2h7v-4372-f6x2?

O3 pinpoints whether GHSA-2h7v-4372-f6x2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2h7v-4372-f6x2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2h7v-4372-f6x2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2h7v-4372-f6x2 published, and has it been updated?

GHSA-2h7v-4372-f6x2 was published on May 4, 2026 and was last updated on May 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-2h7v-4372-f6x2

GHSA-2h7v-4372-f6x2 is a security vulnerability in getkirby/cms. O3 Security confirms whether GHSA-2h7v-4372-f6x2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Kirby CMS's read access to site, user and role information is not gated by permissions

Also known asCVE-2026-42069

Published

May 4, 2026

Updated

May 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Real-World Exposure

2 pkgs affected

🐘getkirby/cms🐘getkirby/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

TL;DR

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

This vulnerability is of high severity for affected sites.

Sites using Kirby are not affected if they intend all users of the site to be able to list and access the site model and all users and roles, including the content stored within these models. Write actions are not affected by this vulnerability as they were gated by permissions before.

Introduction

Missing authorization allows authenticated users to perform actions they are not intended to have access to.

The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information.

Impact

Kirby's user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (site/blueprints/users/...). It is also possible to customize the permissions for each target model in the model blueprints (such as in site/blueprints/pages/...) using the options feature. The permissions and options together control the authorization of user actions.

In affected releases, Kirby did not provide permission settings that control the access to the site model as well as to users and user roles. If the site developer disabled all permissions via the wildcard "*": false setting, this only disabled the actions that were explicitly gated by existing permissions.

To be specific, the following permissions were missing in affected releases and have been added in the patches:

site.access
user.access and users.access (for the own user and other users respectively)
user.list and users.list (for the own user and other users respectively)

Access to role information such as the list of existing roles, their names and descriptions as well as their configured permissions were also not gated by user-based permissions.

Patches

The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. Please update to one of these or a later version to fix the vulnerability.

In all of the mentioned releases, Kirby has added the missing permissions that are listed in the "Impact" section. The user.access and users.access permissions also take effect on the access to the user's own role and to other roles respectively.

Credits

Kirby thanks @HuajiHD for responsibly reporting the identified issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`getkirby/cms`	all versions	4.9.0
🐘Packagist	`getkirby/cms`	≥ 5.0.0&&< 5.4.0	5.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update getkirby/cms to 4.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2h7v-4372-f6x2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2h7v-4372-f6x2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2h7v-4372-f6x2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### TL;DR This vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users. **This vulnerability is of high severity for affected sites.** Sites using Kirby are *not* affected if they intend all users of the site to be able to list and access the site model and all users and roles, including the content stored within these models. Write actions are *not* affected by this vulnerability as they were gated by permissions before. ---- ### Introduction Missing authorization allows authenticated users to perform actions they are not inten

O3 Security · Impact-Aware SCA

Is GHSA-2h7v-4372-f6x2 in your dependencies?

O3 detects GHSA-2h7v-4372-f6x2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works