CVE-2026-40099

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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. For pages, Kirby provides the pages.create and pages.changeStatus permissions (among others). Prior to versions 4.9.0 and 5.4.0, Kirby checked these permissions independently and only for the respective action. However the changeStatus permission didn't take effect on page creation. New pages are created as drafts by default and need to be published by changing the page status of an existing page draft. This is ensured when the page is created via the Kirby Panel. However the REST API allows to override the isDraft flag when creating a new page. This allowed authenticated attackers with the pages.create permission to immediately create published pages, bypassing the normal editorial workflow. The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. Kirby has added a check to the page creation rules that ensures that users without the pages.changeStatus permission cannot create published pages, only page drafts.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
19.4%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 27, 2026

Advisory Details (3)

Auto-updated Jun 14, 2026
Patch available. Sources: github_release, github.
github Patch Available

Page creation API bypasses `changeStatus` permission check via unfiltered `isDraft` parameter · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-w942-j9r6-hr6r
github_release Patch Available

5.4.0

Patch available: getkirby/kirby 5.4.0

https://github.com/getkirby/kirby/releases/tag/5.4.0
github_release Patch Available

4.9.0

Patch available: getkirby/kirby 4.9.0

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
getkirby/cms5.0.0 ... 5.3.3 (21 versions)5.4.0

Weakness Classification(1)

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

Frequently asked(5)

What is CVE-2026-40099?
CVE-2026-40099 is a medium vulnerability 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 CVE-2026-40099 disclosed?
CVE-2026-40099 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40099 actively exploited?
CVE-2026-40099 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40099?
CVE-2026-40099 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-40099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40099, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-40099?

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