{"items":[{"id":"NVI-00002569","kind":"vulnerability","title":"Kirby: System path exposure from error messages in the REST API","revision":5,"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-rf2p-vh74-7vvh","CVE-2026-69127"],"plain_summary":"GitHub lists this reviewed advisory for getkirby/cms, getkirby/cms. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-12f11840cfc72c2304e4d52d1186e095"],"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},{"summary":"The original advisory lists fixed boundaries 4.9.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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 5.5.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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":[{"kind":"CVSS","as_of":"2026-10-24T16:10:00.153Z","value":"6.9 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5df496b9511a4b9f4ea67de0638d18c7"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.699%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53146. Missing scores are unknown.","source_id":"sr-12f11840cfc72c2304e4d52d1186e095"}],"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-1833ed96c90ec5e54b818cc95e67185b","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"},{"id":"sr-1d872eda2991af6e0ea6aad376287dec","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.362Z"},{"id":"sr-5df496b9511a4b9f4ea67de0638d18c7","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-69127","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-69127","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:49.802Z"},{"id":"sr-12f11840cfc72c2304e4d52d1186e095","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-2026-69127","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.861Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1833ed96c90ec5e54b818cc95e67185b"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["<= 4.9.4"]},{"certainty":"source_listed","source_ids":["sr-1833ed96c90ec5e54b818cc95e67185b"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":[">= 5.0.0, < 5.5.2"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.9.5"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.5.2"]}],"null_published_at":"2026-11-04T10:04:47.614Z","source_updated_at":"2026-09-01T16:37:50.000Z","source_disclosed_at":"2026-09-01T16:37: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:41.362Z"},{"id":"NVI-00002569","kind":"vulnerability","title":"Kirby: System path exposure from error messages in the REST API","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-rf2p-vh74-7vvh","CVE-2026-69127"],"plain_summary":"GitHub lists this reviewed advisory for getkirby/cms, getkirby/cms. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-229ac73a32948c030563a1e14c4a7dae"],"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},{"summary":"The original advisory lists fixed boundaries 4.9.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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 5.5.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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":[{"kind":"CVSS","as_of":"2026-10-24T16:10:00.153Z","value":"6.9 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5df496b9511a4b9f4ea67de0638d18c7"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.699%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53159. Missing scores are unknown.","source_id":"sr-229ac73a32948c030563a1e14c4a7dae"}],"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-1833ed96c90ec5e54b818cc95e67185b","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"},{"id":"sr-1d872eda2991af6e0ea6aad376287dec","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.362Z"},{"id":"sr-5df496b9511a4b9f4ea67de0638d18c7","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-69127","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-69127","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:49.802Z"},{"id":"sr-229ac73a32948c030563a1e14c4a7dae","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-2026-69127","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.384Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1833ed96c90ec5e54b818cc95e67185b"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["<= 4.9.4"]},{"certainty":"source_listed","source_ids":["sr-1833ed96c90ec5e54b818cc95e67185b"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":[">= 5.0.0, < 5.5.2"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.9.5"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.5.2"]}],"null_published_at":"2026-11-02T20:21:10.275Z","source_updated_at":"2026-09-01T16:37:50.000Z","source_disclosed_at":"2026-09-01T16:37: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:41.362Z"},{"id":"NVI-00002569","kind":"vulnerability","title":"Kirby: System path exposure from error messages in the REST API","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rf2p-vh74-7vvh","CVE-2026-69127"],"plain_summary":"GitHub lists this reviewed advisory for getkirby/cms, getkirby/cms. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-229ac73a32948c030563a1e14c4a7dae"],"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},{"summary":"The original advisory lists fixed boundaries 4.9.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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 5.5.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.699%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53159. Missing scores are unknown.","source_id":"sr-229ac73a32948c030563a1e14c4a7dae"}],"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-1833ed96c90ec5e54b818cc95e67185b","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"},{"id":"sr-1d872eda2991af6e0ea6aad376287dec","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.362Z"},{"id":"sr-229ac73a32948c030563a1e14c4a7dae","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-2026-69127","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.384Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1833ed96c90ec5e54b818cc95e67185b"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["<= 4.9.4"]},{"certainty":"source_listed","source_ids":["sr-1833ed96c90ec5e54b818cc95e67185b"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":[">= 5.0.0, < 5.5.2"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.9.5"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.5.2"]}],"null_published_at":"2026-11-02T10:00:37.172Z","source_updated_at":"2026-09-01T16:37:50.000Z","source_disclosed_at":"2026-09-01T16:37: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:41.362Z"},{"id":"NVI-00002569","kind":"vulnerability","title":"Kirby: System path exposure from error messages in the REST API","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rf2p-vh74-7vvh","CVE-2026-69127"],"plain_summary":"OSV carries this publisher advisory for 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 4.9.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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 5.5.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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-229ac73a32948c030563a1e14c4a7dae"],"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.699%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53159. Missing scores are unknown.","source_id":"sr-229ac73a32948c030563a1e14c4a7dae"}],"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-1d872eda2991af6e0ea6aad376287dec","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.362Z"},{"id":"sr-229ac73a32948c030563a1e14c4a7dae","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-2026-69127","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.384Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.9.5"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.5.2"]}],"null_published_at":"2026-10-31T22:27:09.611Z","source_updated_at":"2026-09-01T16:45:03.874Z","source_disclosed_at":"2026-09-01T16:37: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:41.362Z"},{"id":"NVI-00002569","kind":"vulnerability","title":"Kirby: System path exposure from error messages in the REST API","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rf2p-vh74-7vvh","CVE-2026-69127"],"plain_summary":"OSV carries this publisher advisory for 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 4.9.5 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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 5.5.2 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"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-1d872eda2991af6e0ea6aad376287dec","url":"https://github.com/advisories/GHSA-rf2p-vh74-7vvh","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rf2p-vh74-7vvh","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.362Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.9.5"]},{"certainty":"source_listed","source_ids":["sr-1d872eda2991af6e0ea6aad376287dec"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### TL;DR\n\nThis vulnerability affects all Kirby sites that have not disabled the REST API with the `'api' => false` option.\n\nIt was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default `content.salt` or prepare specialized attacks.\n\n----\n\n### Introduction\n\nAn information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.\n\n### Affected components\n\nKirby's REST API at `/api` returns JSON data for each request. If an error occurs during processing of the request, a special error ha","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.5.2"]}],"null_published_at":"2026-10-31T22:00:33.895Z","source_updated_at":"2026-09-01T16:45:03.874Z","source_disclosed_at":"2026-09-01T16:37: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:41.362Z"}],"next_cursor":null,"snapshot_revision":"42594"}