{"items":[{"id":"NVI-00003990","kind":"vulnerability","title":"Cross-site scripting from content entered in the tags and multiselect fields","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rv3r-vqjj-8c76"],"plain_summary":"OSV carries this publisher advisory for 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.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-53509f7794818e4da0974563b0d65ecd"],"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.1 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-53509f7794818e4da0974563b0d65ecd"],"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.4 for getkirby/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-53509f7794818e4da0974563b0d65ecd"],"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-53509f7794818e4da0974563b0d65ecd","url":"https://github.com/advisories/GHSA-rv3r-vqjj-8c76","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rv3r-vqjj-8c76","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.366Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-53509f7794818e4da0974563b0d65ecd"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### Introduction\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of the same or other users. In the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nSuch vulnerabilities are critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\n### Impact\n\nThe tags and multiselect fields allow to select tags from an autocompleted list. The tags field also allows to enter new tags or edit existing tags. Kirby already handled escaping of the autocompleted tags, but unfortunately the Panel used HTML rendering for new or edited tags as well as for custom tags from the content file.\n\nThis allowed **attackers with Panel access** to store malicious HTML code in a tag. The browser of the victim who visited the modified page in the Panel will then have rendered this malicious HTML code.\n\nIt also allowed **self-inflicted XSS attacks** in the tags field (meaning that mal","public_affected_ranges":["ECOSYSTEM: introduced 3.5.7; fixed 3.5.8.1"]},{"certainty":"source_listed","source_ids":["sr-53509f7794818e4da0974563b0d65ecd"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### Introduction\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of the same or other users. In the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nSuch vulnerabilities are critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\n### Impact\n\nThe tags and multiselect fields allow to select tags from an autocompleted list. The tags field also allows to enter new tags or edit existing tags. Kirby already handled escaping of the autocompleted tags, but unfortunately the Panel used HTML rendering for new or edited tags as well as for custom tags from the content file.\n\nThis allowed **attackers with Panel access** to store malicious HTML code in a tag. The browser of the victim who visited the modified page in the Panel will then have rendered this malicious HTML code.\n\nIt also allowed **self-inflicted XSS attacks** in the tags field (meaning that mal","public_affected_ranges":["ECOSYSTEM: introduced 3.6.0; fixed 3.6.6.1"]},{"certainty":"source_listed","source_ids":["sr-53509f7794818e4da0974563b0d65ecd"],"technology":"getkirby/cms","known_exclusions":[],"conditions_summary":"### Introduction\n\nCross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of the same or other users. In the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.\n\nSuch vulnerabilities are critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.\n\n### Impact\n\nThe tags and multiselect fields allow to select tags from an autocompleted list. The tags field also allows to enter new tags or edit existing tags. Kirby already handled escaping of the autocompleted tags, but unfortunately the Panel used HTML rendering for new or edited tags as well as for custom tags from the content file.\n\nThis allowed **attackers with Panel access** to store malicious HTML code in a tag. The browser of the victim who visited the modified page in the Panel will then have rendered this malicious HTML code.\n\nIt also allowed **self-inflicted XSS attacks** in the tags field (meaning that mal","public_affected_ranges":["ECOSYSTEM: introduced 3.7.0; fixed 3.7.4"]}],"null_published_at":"2026-10-31T22:12:52.609Z","source_updated_at":"2025-03-24T14:57:39.691Z","source_disclosed_at":"2022-08-30T20:53:03.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.366Z"}],"next_cursor":null,"snapshot_revision":"42594"}