Insufficient permission checks in the language settings in Kirby CMS
Noroxi assessment
Priority: Monitor (action score 32/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.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: getkirby/cms (Packagist) 3.10.1.1, 3.7.5.5, 3.8.4.4.
Low priority for now. Upgrade to getkirby/cms (Packagist) 3.10.1.1, 3.7.5.5, 3.8.4.4 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 a CMS targeting designers and editors. Kirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions. Permissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code. A permission for updating existing languages has not existed before the patched versions. So disabling the languages.* wildcard permission for a role could not have prohibited updates to existing language definitions. The missing permission checks allowed attackers with Panel access to manipulate the language definitions. The problem has been patched in Kirby 3.6.6.6, Kirby 3.7.5.5, Kirby 3.8.4.4, Kirby 3.9.8.2, Kirby 3.10.1.1, and Kirby 4.3.1. Please update to one of these or a later version to fix the vulnerability. There are no known workarounds for this vulnerability.
- Published
- Aug 29, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-863
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.1
- CNA · GitHub_M
- 8.1
- agree
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
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 helpAffected 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.6.6.6
- getkirby kirby3.7.0 and later · before 3.7.5.5
- getkirby kirby3.8.0 and later · before 3.8.4.4
- getkirby kirby3.9.0 and later · before 3.9.8.2
- getkirby kirby3.10.0 and later · before 3.10.1.1
- getkirby kirby4.0.0 and later · before 4.3.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.6.6.6, >= 3.7.0, < 3.7.5.5, >= 3.8.0, < 3.8.4.4, >= 3.9.0, < 3.9.8.2, >= 3.10.0, < 3.10.1.1, >= 4.0.0, < 4.3.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.1 | 3.10.1.1 |
| Packagist | getkirby/cms | from 3.7.0 · before 3.7.5.5 | 3.7.5.5 |
| Packagist | getkirby/cms | from 3.8.0 · before 3.8.4.4 | 3.8.4.4 |
| Packagist | getkirby/cms | from 3.9.0 · before 3.9.8.2 | 3.9.8.2 |
| Packagist | getkirby/cms | from 4.0.0 · before 4.3.1 | 4.3.1 |
| Packagist | getkirby/cms | before 3.6.6.6 | 3.6.6.6 |
Same product
getkirby: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-38490Kirby XML External Entity (XXE) vulnerability in the XML data handler41Plan
- CVE-2026-44177Kirby: Pre-authentication path traversal and PHP file inclusion during user lookup36Monitor
- CVE-2026-54003Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-26484Feb 22, 2024 · A stored cross-site scripting (XSS) vulnerability in the Edit Content Layout module of Kirby CMS v4.1.0 allows attackers to execute arbitrar24Monitor
- ← EarlierCVE-2024-27087Feb 26, 2024 · Kirby cross-site scripting (XSS) in the link field "Custom" type21Monitor
- Later →CVE-2025-30159May 13, 2025 · Kirby vulnerable to path traversal of snippet names in the `snippet()` helper25Monitor
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.1 | Package registry (OSV) |
| Packagist:getkirby/cms | 3.6.6.6 | Package registry (OSV) |
| Packagist:getkirby/cms | 3.7.5.5 | Package registry (OSV) |
| Packagist:getkirby/cms | 3.8.4.4 | Package registry (OSV) |
| Packagist:getkirby/cms | 3.9.8.2 | Package registry (OSV) |
| Packagist:getkirby/cms | 4.3.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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, 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-21896497 days apartKirby is missing permission checks in the content changes API23Monitor
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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.