{"items":[{"id":"NVI-00004519","kind":"vulnerability","title":"Field injection in the KirbyData text storage handler","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-x5mr-p6v4-wp93","CVE-2023-38488"],"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.5.8.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6.6.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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-408a480660f72c47ac71120da683ae7b"],"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":"CVSS","as_of":"2026-06-17T06:10:17.410Z","value":"7.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-c8f5fafcc0940615578ae36425b44b68"},{"kind":"CVSS","as_of":"2026-06-17T06:10:17.410Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-c8f5fafcc0940615578ae36425b44b68"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.924%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.60439. Missing scores are unknown.","source_id":"sr-408a480660f72c47ac71120da683ae7b"}],"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-69509dd0aedf9d2b04252558dba5c6c2","url":"https://github.com/advisories/GHSA-x5mr-p6v4-wp93","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-x5mr-p6v4-wp93","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.439Z"},{"id":"sr-c8f5fafcc0940615578ae36425b44b68","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-38488","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-38488","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:44.011Z"},{"id":"sr-408a480660f72c47ac71120da683ae7b","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-2023-38488","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.5.8.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.6.0; fixed 3.6.6.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.5.2"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.8.0; fixed 3.8.4.1"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.9.0; fixed 3.9.6"]}],"null_published_at":"2026-11-08T19:53:48.773Z","source_updated_at":"2026-09-10T03:49:24.767Z","source_disclosed_at":"2023-07-28T15:35:47.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:51.439Z"},{"id":"NVI-00004519","kind":"vulnerability","title":"Field injection in the KirbyData text storage handler","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-x5mr-p6v4-wp93","CVE-2023-38488"],"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.5.8.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6.6.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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-6c00c109ae0ef34c5fca1057b21fd63a"],"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":"CVSS","as_of":"2026-06-17T06:10:17.410Z","value":"7.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-c8f5fafcc0940615578ae36425b44b68"},{"kind":"CVSS","as_of":"2026-06-17T06:10:17.410Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-c8f5fafcc0940615578ae36425b44b68"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.924%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.60438. Missing scores are unknown.","source_id":"sr-6c00c109ae0ef34c5fca1057b21fd63a"}],"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-69509dd0aedf9d2b04252558dba5c6c2","url":"https://github.com/advisories/GHSA-x5mr-p6v4-wp93","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-x5mr-p6v4-wp93","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.439Z"},{"id":"sr-c8f5fafcc0940615578ae36425b44b68","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-38488","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-38488","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:44.011Z"},{"id":"sr-6c00c109ae0ef34c5fca1057b21fd63a","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-2023-38488","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.5.8.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.6.0; fixed 3.6.6.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.5.2"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.8.0; fixed 3.8.4.1"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.9.0; fixed 3.9.6"]}],"null_published_at":"2026-11-07T22:29:23.426Z","source_updated_at":"2026-09-10T03:49:24.767Z","source_disclosed_at":"2023-07-28T15:35:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:51.439Z"},{"id":"NVI-00004519","kind":"vulnerability","title":"Field injection in the KirbyData text storage handler","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-x5mr-p6v4-wp93","CVE-2023-38488"],"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.5.8.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6.6.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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-6c00c109ae0ef34c5fca1057b21fd63a"],"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.924%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.60438. Missing scores are unknown.","source_id":"sr-6c00c109ae0ef34c5fca1057b21fd63a"}],"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-69509dd0aedf9d2b04252558dba5c6c2","url":"https://github.com/advisories/GHSA-x5mr-p6v4-wp93","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-x5mr-p6v4-wp93","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.439Z"},{"id":"sr-6c00c109ae0ef34c5fca1057b21fd63a","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-2023-38488","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.5.8.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.6.0; fixed 3.6.6.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.5.2"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.8.0; fixed 3.8.4.1"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.9.0; fixed 3.9.6"]}],"null_published_at":"2026-11-01T19:14:01.572Z","source_updated_at":"2026-09-10T03:49:24.767Z","source_disclosed_at":"2023-07-28T15:35:47.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:51.439Z"},{"id":"NVI-00004519","kind":"vulnerability","title":"Field injection in the KirbyData text storage handler","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-x5mr-p6v4-wp93","CVE-2023-38488"],"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.5.8.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6.6.3 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"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-69509dd0aedf9d2b04252558dba5c6c2","url":"https://github.com/advisories/GHSA-x5mr-p6v4-wp93","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-x5mr-p6v4-wp93","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.439Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.5.8.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.6.0; fixed 3.6.6.3"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.5.2"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.8.0; fixed 3.8.4.1"]},{"certainty":"source_listed","source_ids":["sr-69509dd0aedf9d2b04252558dba5c6c2"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form).\n\nYour Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors.\n\n----\n\n### Introduction\n\nA field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified.\n\nIn a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage.\n\n### Impact\n\nKirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`).\n\nWhen reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator.\n\nWhen writing to a KirbyData file, field separators ","public_affected_ranges":["ECOSYSTEM: introduced 3.9.0; fixed 3.9.6"]}],"null_published_at":"2026-10-31T22:12:57.130Z","source_updated_at":"2026-09-10T03:49:24.767Z","source_disclosed_at":"2023-07-28T15:35:47.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:51.439Z"}],"next_cursor":null,"snapshot_revision":"42594"}