CVE-2025-30159

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2025-14508 (ENISA EUVD) · GHSA-fw82-87p8-v6hp (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 snippet() helper or $kirby->snippet() method with a dynamic snippet name (such as a snippet name that depends on request or user data). Sites that only use fixed calls to the snippet() helper/$kirby->snippet() method (i.e. calls with a simple string for the snippet 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 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. 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, Kirby maintainers have added a check for the snippet path that ensures that the resulting path is contained within the configured snippets root. Snippet paths that point outside of the snippets root will not be loaded.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 13, 2025

Last Modified

August 26, 2025

Advisory Details (4)

Auto-updated Aug 1, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Path traversal of snippet names during file system lookup · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-fw82-87p8-v6hp
GitHub release Patch Available

4.7.1

Patch available: getkirby/kirby 4.7.1

https://github.com/getkirby/kirby/releases/tag/4.7.1
GitHub release Patch Available

3.9.8.3

Patch available: getkirby/kirby 3.9.8.3

https://github.com/getkirby/kirby/releases/tag/3.9.8.3
GitHub release Patch Available

3.10.1.2

Patch available: getkirby/kirby 3.10.1.2

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

Vendor Advisories for CVE-2025-30159(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composergetkirby/kirby @ 3.9.8.3 (fixes < 3.9.8.3)—ghsa
composergetkirby/kirby @ 3.10.1.2 (fixes >= 3.10.0, < 3.10.1.2)—ghsa
composergetkirby/kirby @ 4.7.1 (fixes >= 4.0.0, < 4.7.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
getkirby/kirby2.4.0 ... 2.5.9-RC-2 (25 versions)
  • every version up to 3.9.8.3: fixed in 3.9.8.3
  • 3.10.0 up to 3.10.1.2: fixed in 3.10.1.2
  • 4.0.0 up to 4.7.1: fixed in 4.7.1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 250 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:49 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-11-13 08:10 UTCEchelonGraph re-scored
  3. 2026-11-13 08:10 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-11-12 09:29 UTCEchelonGraph re-scored
  6. 2026-11-12 09:29 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  7. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-11 10:51 UTCEchelonGraph re-scored
  9. 2026-11-11 10:51 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  10. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  11. 2026-11-10 12:12 UTCEchelonGraph re-scored
  12. 2026-11-10 12:12 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  13. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-11-09 13:33 UTCEchelonGraph re-scored
  15. 2026-11-09 13:33 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  16. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-08 14:55 UTCEchelonGraph re-scored
  18. 2026-11-08 14:55 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  19. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-11-07 16:17 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  21. 2026-11-06 17:36 UTCEchelonGraph re-scored
  22. 2026-11-06 17:36 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  23. 2026-11-06 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-11-05 18:58 UTCEchelonGraph re-scored
  25. 2026-11-05 18:58 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
Show 74 more
  1. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-05 11:25 UTCOSV refresh
  3. 2026-11-04 20:20 UTCEchelonGraph re-scored
  4. 2026-11-04 20:20 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  5. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-03 21:41 UTCEchelonGraph re-scored
  7. 2026-11-03 21:41 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  8. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-11-02 23:03 UTCEchelonGraph re-scored
  10. 2026-11-02 23:03 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  11. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-11-02 00:25 UTCEchelonGraph re-scored
  13. 2026-11-02 00:25 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  14. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-11-01 08:07 UTCGHSA enrichmentGHSA-fw82-87p8-v6hp · GitHub severity MODERATE
  16. 2026-11-01 01:47 UTCEchelonGraph re-scored
  17. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-31 03:08 UTCEchelonGraph re-scored
  19. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-30 04:30 UTCEchelonGraph re-scored
  21. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-29 05:52 UTCEchelonGraph re-scored
  23. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-28 07:13 UTCEchelonGraph re-scored
  25. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-27 08:35 UTCEchelonGraph re-scored
  27. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-25 16:37 UTCEchelonGraph re-scored
  29. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-25 09:14 UTCEchelonGraph re-scored
  31. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-24 10:35 UTCEchelonGraph re-scored
  33. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-10-23 11:56 UTCEchelonGraph re-scored
  35. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  36. 2026-10-22 13:18 UTCEchelonGraph re-scored
  37. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  38. 2026-10-21 14:40 UTCEchelonGraph re-scored
  39. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-10-20 15:22 UTCEchelonGraph re-scored
  41. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  42. 2026-10-18 17:22 UTCEchelonGraph re-scored
  43. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  44. 2026-10-18 05:40 UTCEchelonGraph re-scored
  45. 2026-10-17 18:42 UTCEchelonGraph re-scored
  46. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  47. 2026-10-16 20:03 UTCEchelonGraph re-scored
  48. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  49. 2026-10-15 17:36 UTCEchelonGraph re-scored
  50. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  51. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  52. 2026-10-14 11:24 UTCEchelonGraph re-scored
  53. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  54. 2026-10-12 17:13 UTCEchelonGraph re-scored
  55. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  56. 2026-10-11 20:45 UTCEchelonGraph re-scored
  57. 2026-10-11 18:55 UTCEchelonGraph re-scored
  58. 2026-10-11 15:33 UTCEchelonGraph re-scored
  59. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  60. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  62. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  64. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-10-02 14:11 UTCOSV refresh
  69. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  72. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  73. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  74. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Related CVEs(same product + same CWE)

Same product

1 shown

Packagist:getkirby/kirby

Frequently asked(5)

What is CVE-2025-30159?
CVE-2025-30159 is a critical-severity vulnerability; its CVE record was published on May 13, 2025. 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 snippet() helper or $kirby->snippet() method with a dynamic snippet name (such as a snippet name that depends on request or user data). Sites…
When was the CVE record for CVE-2025-30159 published?
The CVE record for CVE-2025-30159 was published on May 13, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 26, 2025; the record at its source may have been updated since.
Is CVE-2025-30159 actively exploited?
CVE-2025-30159 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-30159?
CVE-2025-30159 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-30159?
A fix for CVE-2025-30159 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-30159 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-30159

Explore →

Is Your Infrastructure Affected by CVE-2025-30159?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs