← Back to results
Vulnerability record · public intelligence
CVE-2025-30159
CRITICAL

Kirby vulnerable to path traversal of snippet names in the `snippet()` helper

Published May 13, 2025 · Updated Oct 23, 2026 · Also known as GHSA-fw82-87p8-v6hp

Severity · CVSSCRITICAL · 9.1
Known exploitationNot listed
EPSS / likelihood0.71%
QFinch risk score20 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

Kirby vulnerable to path traversal of snippet names in the `snippet()` helper

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

This vulnerability affects all Kirby sites that use the `snippet()` helper or `$kirby->snippet()` method with a dynamic snippet name (such as a snippet name that depends on request or user data).

Potential impact

The missing path traversal check allowed attackers to navigate and access all files on the server that were accessible to the PHP process, including files outside of the snippets root or even outside of the Kirby installation. PHP code within such files was executed. Such attacks first require an attack vector in the site code that is caused by dynamic snippet names, such as snippet('tags-' . get('tags')). It generally also requires knowledge of the site structure and the server's file system by the attacker, although it can be possible to find vulnerable setups through automated methods such as fuzzing. In a vulnerable setup, this could cause damage to the confidentiality and integrity of the server, for example: - it could allow the attacker to build a map of the server's file system for subsequent attacks, - it could allow access to configuration files that may contain sensitive information like security tokens or - it could cause the unintended execution of PHP scripts.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
20%
Aliases
GHSA-fw82-87p8-v6hp

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Source repository ↗

Record history

Published May 13, 2025 · Last refreshed Oct 23, 2026