CVE-2025-30207
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKirby 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in Kirby CMS versions prior to 3.9.8.3, 3.10.1.2, and 4.7.1 allows attackers to detect file existence on the server when using PHP's built-in web server. The router delegates requests for existing files to PHP without validating they are within the document root, enabling attackers to enumerate files outside the web root by observing different HTTP responses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.9.8.3>= 3.10.0, < 3.10.1.2>= 4.0.0, < 4.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Kirby CMS versionLocate the version file or header in your Kirby installation (typically in composer.json, kirby version constant, or admin panel about page) and note the exact version numberAffected if Version is below 3.9.8.3, or between 3.10.0 and 3.10.1.1 inclusive, or between 4.0.0 and 4.7.0 inclusive
-
Determine web server typeCheck the server configuration or process manager to identify whether PHP's built-in development server (php -S) is running the application rather than Apache, nginx, or CaddyAffected if PHP's built-in web server is being used to serve the Kirby site
-
Verify PHP built-in server router behaviorStart the PHP built-in server with the Kirby index.php as router and attempt requests for files outside the document root, observing whether different HTTP status codes reveal file existenceAffected if The router script delegates to PHP without validating file paths are within document root, allowing traversal-based file detection
You are affected if your Kirby version falls within the vulnerable ranges AND you are using PHP's built-in web server to serve the application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.9.8.33.10.1.24.7.1
Upgrade to Kirby 3.9.8.3, 3.10.1.2, or 4.7.1 or later. If using PHP's built-in server in production, migrate to a proper web server (Apache, nginx, or Caddy) as recommended by Kirby.
Kirby 3.9.8.3 (for 3.9.x branch), Kirby 3.10.1.2 (for 3.10.x branch), or Kirby 4.7.1 (for 4.x branch)
- Identify the current Kirby version by checking the composer.json or kirby version file
- If running version < 3.9.8.3 but >= 3.9.0: upgrade to Kirby 3.9.8.3
- If running version >= 3.10.0 and < 3.10.1.2: upgrade to Kirby 3.10.1.2
- If running version >= 4.0.0 and < 4.7.1: upgrade to Kirby 4.7.1
- After upgrading, verify the installation works correctly
- Note: This vulnerability only affects PHP's built-in server (development environments). Production sites using Apache, nginx, or Caddy are not affected.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30207 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data