{"items":[{"id":"NVI-00007862","kind":"vulnerability","title":"Kirby has insufficient permission checks in the language settings","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jm9m-rqr3-wfmh","CVE-2024-41964"],"plain_summary":"OSV carries this publisher advisory for getkirby/cms, getkirby/cms, getkirby/cms, getkirby/cms, getkirby/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 3.6.6.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.7.5.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.8.4.4 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.9.8.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.10.1.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.3.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-d93f667e31f4a1365097abcc31a8120f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.480%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.41418. Missing scores are unknown.","source_id":"sr-d93f667e31f4a1365097abcc31a8120f"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-eb8c983f4b0d17b41c91fcdeaf933146","url":"https://github.com/advisories/GHSA-jm9m-rqr3-wfmh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jm9m-rqr3-wfmh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.967Z"},{"id":"sr-d93f667e31f4a1365097abcc31a8120f","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-41964","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.368Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.6.6.6"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.5.5"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.8.0; fixed 3.8.4.4"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.9.0; fixed 3.9.8.2"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.10.0; fixed 3.10.1.1"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.3.1"]}],"null_published_at":"2026-11-08T08:10:32.020Z","source_updated_at":"2024-08-29T21:41:06.370Z","source_disclosed_at":"2024-08-29T17:55:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.967Z"},{"id":"NVI-00007862","kind":"vulnerability","title":"Kirby has insufficient permission checks in the language settings","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jm9m-rqr3-wfmh","CVE-2024-41964"],"plain_summary":"OSV carries this publisher advisory for getkirby/cms, getkirby/cms, getkirby/cms, getkirby/cms, getkirby/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 3.6.6.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.7.5.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.8.4.4 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.9.8.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.10.1.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.3.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-eb8c983f4b0d17b41c91fcdeaf933146","url":"https://github.com/advisories/GHSA-jm9m-rqr3-wfmh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jm9m-rqr3-wfmh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.967Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.6.6.6"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.5.5"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.8.0; fixed 3.8.4.4"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.9.0; fixed 3.9.8.2"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 3.10.0; fixed 3.10.1.1"]},{"certainty":"source_listed","source_ids":["sr-eb8c983f4b0d17b41c91fcdeaf933146"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites with enabled `languages` option that might have potential attackers in the group of authenticated Panel users.\n\nIf you have disabled the `languages` and/or `api` option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is *not* affected.\n\n----\n\n### Introduction\n\nKirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.\n\nPermissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.\n\nA 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.\n\n### Impact\n\nThe missing permission checks allowed attackers with Panel access to manipulate the language definitions.\n\nThe language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:\n\n- If the `language","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.3.1"]}],"null_published_at":"2026-10-31T22:13:18.638Z","source_updated_at":"2024-08-29T21:41:06.370Z","source_disclosed_at":"2024-08-29T17:55:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.967Z"}],"next_cursor":null,"snapshot_revision":"42594"}