Skip to main content

CVE-2025-30207: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in getkirby kirby

Low
VulnerabilityCVE-2025-30207cvecve-2025-30207cwe-22cwe-23
Published: Tue May 13 2025 (05/13/2025, 15:20:00 UTC)
Source: CVE
Vendor/Project: getkirby
Product: kirby

Description

Kirby is an open-source content management system. A vulnerability in versions prior to 3.9.8.3, 3.10.1.2, and 4.7.1 affects all Kirby setups that use PHP's built-in server. Such setups are commonly only used during local development. Sites that use other server software (such as Apache, nginx or Caddy) are not affected. A missing path traversal check allowed attackers to navigate all files on the server that were accessible to the PHP process, including files outside of the Kirby installation. The vulnerable implementation delegated all existing files to PHP, including existing files outside of the document root. This leads to a different response that allows attackers to determine whether the requested file exists. Because Kirby's router only delegates such requests to PHP and does not load or execute them, contents of the files were not exposed as PHP treats requests to files outside of the document root as invalid. The problem has been patched in Kirby 3.9.8.3, Kirby 3.10.1.2, and Kirby 4.7.1. In all of the mentioned releases, the maintainers of Kirby have updated the router to check if existing static files are within the document root. Requests to files outside the document root are treated as page requests of the error page and will no longer allow to determine whether the file exists or not.

AI-Powered Analysis

AILast updated: 07/06/2025, 17:56:47 UTC

Technical Analysis

CVE-2025-30207 is a path traversal vulnerability identified in the Kirby content management system (CMS), specifically affecting versions prior to 3.9.8.3, between 3.10.0 and 3.10.1.2, and between 4.0.0 and 4.7.1. Kirby is an open-source CMS primarily used for website content management. The vulnerability arises in setups where Kirby is run using PHP's built-in web server, which is typically used only during local development environments rather than production. The root cause is a missing validation check in Kirby's router component that allowed attackers to perform path traversal attacks by requesting files outside the intended document root directory. This flaw permitted attackers to probe the server filesystem accessible to the PHP process and determine the existence of arbitrary files outside the Kirby installation directory. However, because the PHP built-in server treats requests to files outside the document root as invalid and Kirby’s router only delegates such requests without executing them, the contents of these files were not disclosed, limiting the impact to information disclosure about file existence only. The vulnerability does not affect Kirby installations running on other common web servers such as Apache, nginx, or Caddy. The issue was addressed in Kirby versions 3.9.8.3, 3.10.1.2, and 4.7.1 by adding strict checks in the router to ensure that only files within the document root are served, and any requests for files outside this root are handled as error page requests, preventing attackers from confirming file existence. The CVSS 4.0 base score is 2.3, indicating a low severity vulnerability, with an attack vector requiring adjacent network access, no privileges or user interaction, and limited scope and impact.

Potential Impact

For European organizations, the direct impact of this vulnerability is limited due to its low severity and the specific conditions required for exploitation. Since the vulnerability only affects Kirby CMS instances running on PHP's built-in server, which is predominantly used for local development rather than production, the risk to live, internet-facing systems is minimal. The vulnerability allows attackers to confirm the existence of files on the server accessible to PHP, which could aid in reconnaissance activities during an attack chain but does not expose file contents or allow code execution. Consequently, confidentiality, integrity, and availability impacts are negligible. However, organizations that use Kirby CMS for development or staging environments on local or internal networks could be at some risk if these environments are accessible to attackers, such as through misconfigured VPNs or internal network exposure. Attackers could leverage this information to map the filesystem and identify sensitive files or configuration files, potentially facilitating further targeted attacks. Overall, the threat is low but should not be ignored in secure development lifecycle practices.

Mitigation Recommendations

European organizations using Kirby CMS should ensure that all instances are updated to the patched versions: 3.9.8.3, 3.10.1.2, or 4.7.1 or later. Beyond applying patches, organizations should avoid using PHP’s built-in server for anything other than isolated local development environments that are not accessible externally. Development environments should be segregated from production and protected by network access controls such as firewalls or VPNs to prevent unauthorized access. Additionally, organizations should implement strict access controls on development machines and internal networks to limit exposure. Monitoring and logging access to development servers can help detect suspicious activity. For environments where PHP’s built-in server must be used, consider additional web server-level access restrictions or sandboxing to prevent unauthorized file system access. Regular security reviews of development and staging environments should be conducted to ensure no inadvertent exposure. Finally, educating developers and IT staff about the risks of using PHP’s built-in server in accessible environments will help reduce the attack surface.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-03-18T18:15:13.849Z
Cisa Enriched
true
Cvss Version
4.0
State
PUBLISHED

Threat ID: 682cd0fc1484d88663aecc34

Added to database: 5/20/2025, 6:59:08 PM

Last enriched: 7/6/2025, 5:56:47 PM

Last updated: 7/26/2025, 3:00:45 AM

Views: 8

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats