How severe is GHSA-g3h8-cg9x-47qw?

GHSA-g3h8-cg9x-47qw has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g3h8-cg9x-47qw?

GHSA-g3h8-cg9x-47qw affects the following packages: getkirby/panel (Packagist), getkirby/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g3h8-cg9x-47qw?

Update getkirby/panel to 2.5.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3h8-cg9x-47qw is resolved across your whole dependency graph.

How do I detect GHSA-g3h8-cg9x-47qw in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/panel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g3h8-cg9x-47qw if there is no patch (or I can't update yet)?

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Is GHSA-g3h8-cg9x-47qw actively exploited in the wild?

No public exploit code has been indexed for GHSA-g3h8-cg9x-47qw 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.

What is the EPSS score for GHSA-g3h8-cg9x-47qw?

GHSA-g3h8-cg9x-47qw has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g3h8-cg9x-47qw?

GHSA-g3h8-cg9x-47qw is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g3h8-cg9x-47qw published, and has it been updated?

GHSA-g3h8-cg9x-47qw was published on December 8, 2020 and was last updated on September 10, 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

Not in CISA KEV

MEDIUM severity

Kirby Panel users could upload PHP Phar archives as content files before v2.5.14 and v3.4.5GHSA-g3h8-cg9x-47qw

MEDIUMFix: getkirby-v2/panel@5a569d4

GHSA-g3h8-cg9x-47qw is a medium-severity (CVSS 6.8) Unrestricted File Upload vulnerability in getkirby/panel. A fix is available for getkirby/panel — see the affected versions and patch details below.

Also known asCVE-2020-26255

Published

Dec 8, 2020

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-g3h8-cg9x-47qw by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐘getkirby/panel🐘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

Impact

An editor with full access to the Kirby Panel can upload a PHP .phar file and execute it on the server. This vulnerability is critical if you might have potential attackers in your group of authenticated Panel users, as they can gain access to the server with such a Phar file.

Visitors without Panel access cannot use this attack vector.

Patches

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

Note: Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.

Workarounds

Kirby 2 sites on older releases can also be patched by applying the changes from this commit.

Credits

Thanks to Thore Imhof of Accenture for reporting the problem.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`getkirby/panel`	all versions	2.5.14`composer require getkirby/panel:^2.5.14`
🐘Packagist	`getkirby/cms`	≥ 3.0.0&&< 3.4.5	3.4.5`composer require getkirby/cms:^3.4.5`

Affected Products

2 products · 2 configurations

Application

kirbygetkirby

< 3.4.5

range

Application

panelgetkirby

< 2.5.14

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/panel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update getkirby/panel to 2.5.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3h8-cg9x-47qw is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

### Impact An editor with full access to the Kirby Panel can upload a PHP `.phar` file and execute it on the server. This vulnerability is critical if you might have potential attackers in your group of authenticated Panel users, as they can gain access to the server with such a Phar file. Visitors without Panel access *cannot* use this attack vector. ### Patches The problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.4.5](https://github.com/getkirby/kirby/releases/tag/3.4.5). Please update to one of these or a [later version](h