{"items":[{"id":"NVI-00002080","kind":"vulnerability","title":"Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hph3-hv3c-7725","CVE-2023-22489"],"plain_summary":"OSV carries this publisher advisory for flarum/core. 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 1.6.3 for flarum/core. Confirm the publisher’s latest guidance.","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"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-0659c66bd75d93027e6f039ea34ee0ec"],"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-11-03T12:00:27.000Z","value":"0.580%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.4776. Missing scores are unknown.","source_id":"sr-0659c66bd75d93027e6f039ea34ee0ec"}],"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-0a8aae9bb539125f45431fa0e908c5ae","url":"https://github.com/advisories/GHSA-hph3-hv3c-7725","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hph3-hv3c-7725","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.431Z"},{"id":"sr-0659c66bd75d93027e6f039ea34ee0ec","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-22489","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"technology":"flarum/core","known_exclusions":[],"conditions_summary":"If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.\n\nThis includes users that don't have a validated email.\n\nGuests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.\n\nThis happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies.\n\nFlarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion.\n\n### Impact\nThis can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to.\n\nIn combination with the e","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.6.3"]}],"null_published_at":"2026-11-04T10:04:41.551Z","source_updated_at":"2023-11-08T04:11:36.542Z","source_disclosed_at":"2023-01-10T22:28:19.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:20.431Z"},{"id":"NVI-00002080","kind":"vulnerability","title":"Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hph3-hv3c-7725","CVE-2023-22489"],"plain_summary":"OSV carries this publisher advisory for flarum/core. 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 1.6.3 for flarum/core. Confirm the publisher’s latest guidance.","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"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-0830edbf7317455f26359e590274ee8b"],"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-11-02T12:00:30.000Z","value":"0.580%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47712. Missing scores are unknown.","source_id":"sr-0830edbf7317455f26359e590274ee8b"}],"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-0a8aae9bb539125f45431fa0e908c5ae","url":"https://github.com/advisories/GHSA-hph3-hv3c-7725","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hph3-hv3c-7725","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.431Z"},{"id":"sr-0830edbf7317455f26359e590274ee8b","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-22489","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"technology":"flarum/core","known_exclusions":[],"conditions_summary":"If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.\n\nThis includes users that don't have a validated email.\n\nGuests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.\n\nThis happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies.\n\nFlarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion.\n\n### Impact\nThis can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to.\n\nIn combination with the e","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.6.3"]}],"null_published_at":"2026-11-03T17:49:15.023Z","source_updated_at":"2023-11-08T04:11:36.542Z","source_disclosed_at":"2023-01-10T22:28:19.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:20.431Z"},{"id":"NVI-00002080","kind":"vulnerability","title":"Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hph3-hv3c-7725","CVE-2023-22489"],"plain_summary":"OSV carries this publisher advisory for flarum/core. 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 1.6.3 for flarum/core. Confirm the publisher’s latest guidance.","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"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-0b017e01f049f2aef32f05f8e554816d"],"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.580%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47732. Missing scores are unknown.","source_id":"sr-0b017e01f049f2aef32f05f8e554816d"}],"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-0a8aae9bb539125f45431fa0e908c5ae","url":"https://github.com/advisories/GHSA-hph3-hv3c-7725","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hph3-hv3c-7725","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.431Z"},{"id":"sr-0b017e01f049f2aef32f05f8e554816d","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-22489","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"technology":"flarum/core","known_exclusions":[],"conditions_summary":"If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.\n\nThis includes users that don't have a validated email.\n\nGuests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.\n\nThis happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies.\n\nFlarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion.\n\n### Impact\nThis can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to.\n\nIn combination with the e","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.6.3"]}],"null_published_at":"2026-10-31T22:13:44.228Z","source_updated_at":"2023-11-08T04:11:36.542Z","source_disclosed_at":"2023-01-10T22:28:19.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:20.431Z"},{"id":"NVI-00002080","kind":"vulnerability","title":"Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hph3-hv3c-7725","CVE-2023-22489"],"plain_summary":"OSV carries this publisher advisory for flarum/core. 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 1.6.3 for flarum/core. Confirm the publisher’s latest guidance.","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"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-0a8aae9bb539125f45431fa0e908c5ae","url":"https://github.com/advisories/GHSA-hph3-hv3c-7725","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hph3-hv3c-7725","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.431Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0a8aae9bb539125f45431fa0e908c5ae"],"technology":"flarum/core","known_exclusions":[],"conditions_summary":"If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.\n\nThis includes users that don't have a validated email.\n\nGuests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.\n\nThis happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies.\n\nFlarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion.\n\n### Impact\nThis can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to.\n\nIn combination with the e","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.6.3"]}],"null_published_at":"2026-10-31T21:53:28.064Z","source_updated_at":"2023-11-08T04:11:36.542Z","source_disclosed_at":"2023-01-10T22:28: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:42:20.431Z"}],"next_cursor":null,"snapshot_revision":"42594"}