{"items":[{"id":"NVI-00004763","kind":"vulnerability","title":"Kirby .dev domains and some reverse proxy setups were treated as local","revision":2,"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-2ccx-2gf3-8xvv","CVE-2020-26253"],"plain_summary":"OSV carries this publisher advisory for getkirby/panel, 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 2.5.14 for getkirby/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"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.3.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"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-d97822e022f06fe520f38727610f0bfc"],"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-17T03:07:55.617Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-d97822e022f06fe520f38727610f0bfc"},{"kind":"CVSS","as_of":"2026-06-17T03:07:55.617Z","value":"6.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-d97822e022f06fe520f38727610f0bfc"},{"kind":"CVSS","as_of":"2026-06-17T03:07:55.617Z","value":"5.9 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-d97822e022f06fe520f38727610f0bfc"}],"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-724644ce57c8d5611df80b034615fc16","url":"https://github.com/advisories/GHSA-2ccx-2gf3-8xvv","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2ccx-2gf3-8xvv","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.014Z"},{"id":"sr-d97822e022f06fe520f38727610f0bfc","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26253","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2020-26253","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:13.751Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"technology":"getkirby/panel","known_exclusions":[],"conditions_summary":"### Impact\n\n#### About our registration block\n\nIn order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server. \n\nIn this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.\n\nTo be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site. \n\n#### The issue\n\nAs noted by Jukka Rautanen, this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our in","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.5.14"]},{"certainty":"source_listed","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### Impact\n\n#### About our registration block\n\nIn order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server. \n\nIn this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.\n\nTo be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site. \n\n#### The issue\n\nAs noted by Jukka Rautanen, this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our in","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.3.6"]}],"null_published_at":"2026-10-31T22:27:12.414Z","source_updated_at":"2026-07-08T06:00:54.273Z","source_disclosed_at":"2021-01-14T19:15:19.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:41:40.014Z"},{"id":"NVI-00004763","kind":"vulnerability","title":"Kirby .dev domains and some reverse proxy setups were treated as local","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2ccx-2gf3-8xvv","CVE-2020-26253"],"plain_summary":"OSV carries this publisher advisory for getkirby/panel, 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 2.5.14 for getkirby/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"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.3.6 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"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-724644ce57c8d5611df80b034615fc16","url":"https://github.com/advisories/GHSA-2ccx-2gf3-8xvv","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2ccx-2gf3-8xvv","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.014Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"technology":"getkirby/panel","known_exclusions":[],"conditions_summary":"### Impact\n\n#### About our registration block\n\nIn order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server. \n\nIn this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.\n\nTo be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site. \n\n#### The issue\n\nAs noted by Jukka Rautanen, this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our in","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.5.14"]},{"certainty":"source_listed","source_ids":["sr-724644ce57c8d5611df80b034615fc16"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### Impact\n\n#### About our registration block\n\nIn order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server. \n\nIn this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.\n\nTo be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site. \n\n#### The issue\n\nAs noted by Jukka Rautanen, this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our in","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.3.6"]}],"null_published_at":"2026-10-31T22:12:57.141Z","source_updated_at":"2026-07-08T06:00:54.273Z","source_disclosed_at":"2021-01-14T19:15:19.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:41:40.014Z"}],"next_cursor":null,"snapshot_revision":"42594"}