NVD / CVE Program· CNA GitHub_M

CVE-2025-31493: Path traversal of collection names during file system lookup

Noroxi assessment

Priority: Monitor (action score 25/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: getkirby/cms (Packagist) 3.10.1.2, 4.7.1, 3.9.8.3.

Low priority for now. Upgrade to getkirby/cms (Packagist) 3.10.1.2, 4.7.1, 3.9.8.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 sites that use the `collection()` helper or `$kirby->collection()` method with a dynamic collection name (such as a collection name that depends on request or user data). Sites that only use fixed calls to the `collection()` helper/`$kirby->collection()` method (i.e. calls with a simple string for the collection name) are *not* affected. A 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 collections 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 collection names, such as `collection('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. 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 added a check for the collection path that ensures that the resulting path is contained within the configured collections root. Collection paths that point outside of the collections root will not be loaded.

MediumCVSS 6.3 · v4.0—No exploit Fix available

GHSA-x275-h9j4-7p4h

Published: May 13, 2025
Updated: Jun 17, 2026
EPSS: 0.5% · 48th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.3; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
getkirby	kirby	cpe:2.3:a:getkirby:kirby

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

getkirby kirbybefore 3.9.8.3
getkirby kirby3.10.0 and later · before 3.10.1.2
getkirby kirby4.0.0 and later · before 4.7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

getkirby kirby
- < 3.9.8.3, >= 3.10.0, < 3.10.1.2, >= 4.0.0, < 4.7.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	getkirby/cms	from 3.10.0 · before 3.10.1.2	3.10.1.2
Packagist	getkirby/cms	from 4.0.0 · before 4.7.1	4.7.1
Packagist	getkirby/cms	before 3.9.8.3	3.9.8.3

Same product

getkirby: all records

Other highest-scoring records for the same primary product.

CVE-2023-38490Kirby XML External Entity (XXE) vulnerability in the XML data handler
41Plan
CVE-2026-44177Kirby: Pre-authentication path traversal and PHP file inclusion during user lookup
36Monitor
CVE-2026-54003Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header
36Monitor

Published before and after this one in the same product

← EarlierCVE-2025-30159May 13, 2025 · Kirby vulnerable to path traversal of snippet names in the `snippet()` helper
25Monitor
← EarlierCVE-2025-30207May 13, 2025 · Kirby vulnerable to path traversal in the router for PHP's built-in server
9Monitor
Later →CVE-2025-65012Nov 18, 2025 · Kirby CMS has cross-site scripting (XSS) in the changes dialog
20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Packagist:getkirby/cms	3.10.1.2	Package registry (OSV)
Packagist:getkirby/cms	3.9.8.3	Package registry (OSV)
Packagist:getkirby/cms	4.7.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-44177429 days apartKirby: Pre-authentication path traversal and PHP file inclusion during user lookup
36Monitor
CVE-2026-75594475 days apartKirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media handling
32Monitor
CVE-2026-75592475 days apartKirby: Access to image files outside of the site root via path traversal in the media handling
27Monitor
CVE-2025-301590 days apartKirby vulnerable to path traversal of snippet names in the `snippet()` helper
25Monitor
CVE-2025-302070 days apartKirby vulnerable to path traversal in the router for PHP's built-in server
9Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/getkirby/kirby/releases/tag/3.10.1.2

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records