CVE-2026-41325

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (30th 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-2026-25371 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Kirby is an open-source content management system. Kirby's user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (site/blueprints/users/...). It is also possible to customize the permissions for each target model in the model blueprints (such as in site/blueprints/pages/...) using the options feature. The permissions and options together control the authorization of user actions. Kirby provides the pages.create, files.create and users.create permissions (among others). These permissions can again be set in the user blueprint and/or in the blueprint of the target model via options. Prior to versions 4.9.0 and 5.4.0, Kirby allowed to override the options during the creation of pages, files and users by injecting custom dynamic blueprint configuration into the model data. The injected options could include 'create' => true, which then caused an override of the permissions and options configured by the site developer in the user and model blueprints. The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. The patched versions have updated the normalization code that is used during the creation of pages, files and users to include a filter for the blueprint property. This prevents the injection of dynamic blueprint configuration into the creation request.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
30th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

April 24, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated May 2, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Page, file and user creation APIs bypass `create` permission check via unfiltered `blueprint` parameter · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-6gqr-mx34-wh8r
Web page

Release 5.4.0 · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/releases/tag/5.4.0
Web page

Release 4.9.0 · getkirby/kirby · GitHub

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
getkirby/cms5.0.0 ... 5.3.3 (21 versions)
  • every version up to 4.9.0: fixed in 4.9.0
  • 5.0.0 up to 5.4.0: fixed in 5.4.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 40× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 202 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-41325?
CVE-2026-41325 is a high-severity vulnerability; its CVE record was published on April 24, 2026. Kirby is an open-source content management system. Kirby's user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (site/blueprints/users/...). It is also possible to customize…
When was the CVE record for CVE-2026-41325 published?
The CVE record for CVE-2026-41325 was published on April 24, 2026. 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 October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-41325 actively exploited?
CVE-2026-41325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41325?
CVE-2026-41325 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-41325?
A fix for CVE-2026-41325 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41325

Explore →

Is Your Infrastructure Affected by CVE-2026-41325?

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

Book a Demo →Browse All CVEs