{"items":[{"id":"NVI-00003481","kind":"vulnerability","title":"Discoverability of user password hash in Statamic CMS","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-qcgx-7p5f-hxvr","CVE-2022-24784"],"plain_summary":"OSV carries this publisher advisory for statamic/cms, statamic/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.2.39 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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.2 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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-24a5e8b734897bdd7aaf8fa81e5ab5cd"],"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-17T04:32:30.733Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-0a85b9a6a890e1e963e8f11c0581e787"},{"kind":"CVSS","as_of":"2026-06-17T04:32:30.733Z","value":"3.7 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0a85b9a6a890e1e963e8f11c0581e787"},{"kind":"CVSS","as_of":"2026-06-17T04:32:30.733Z","value":"3.7 LOW (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-0a85b9a6a890e1e963e8f11c0581e787"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"1.034%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.63848. Missing scores are unknown.","source_id":"sr-24a5e8b734897bdd7aaf8fa81e5ab5cd"}],"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-402a3bbce429ecfa4e854a6d0b9054e6","url":"https://github.com/advisories/GHSA-qcgx-7p5f-hxvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qcgx-7p5f-hxvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.002Z"},{"id":"sr-0a85b9a6a890e1e963e8f11c0581e787","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-24784","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-24784","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:19.043Z"},{"id":"sr-24a5e8b734897bdd7aaf8fa81e5ab5cd","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-2022-24784","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.2.39"]},{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.2"]}],"null_published_at":"2026-11-08T19:53:33.652Z","source_updated_at":"2024-02-16T08:10:37.547Z","source_disclosed_at":"2022-03-29T22:11:45.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:31.002Z"},{"id":"NVI-00003481","kind":"vulnerability","title":"Discoverability of user password hash in Statamic CMS","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-qcgx-7p5f-hxvr","CVE-2022-24784"],"plain_summary":"OSV carries this publisher advisory for statamic/cms, statamic/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.2.39 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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.2 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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-1a6992895667b610c90d6e0f87ecf08a"],"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-17T04:32:30.733Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-0a85b9a6a890e1e963e8f11c0581e787"},{"kind":"CVSS","as_of":"2026-06-17T04:32:30.733Z","value":"3.7 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0a85b9a6a890e1e963e8f11c0581e787"},{"kind":"CVSS","as_of":"2026-06-17T04:32:30.733Z","value":"3.7 LOW (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-0a85b9a6a890e1e963e8f11c0581e787"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.034%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.63858. Missing scores are unknown.","source_id":"sr-1a6992895667b610c90d6e0f87ecf08a"}],"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-402a3bbce429ecfa4e854a6d0b9054e6","url":"https://github.com/advisories/GHSA-qcgx-7p5f-hxvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qcgx-7p5f-hxvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.002Z"},{"id":"sr-0a85b9a6a890e1e963e8f11c0581e787","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-24784","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-24784","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:19.043Z"},{"id":"sr-1a6992895667b610c90d6e0f87ecf08a","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-2022-24784","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.2.39"]},{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.2"]}],"null_published_at":"2026-11-01T01:04:01.256Z","source_updated_at":"2024-02-16T08:10:37.547Z","source_disclosed_at":"2022-03-29T22:11:45.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:31.002Z"},{"id":"NVI-00003481","kind":"vulnerability","title":"Discoverability of user password hash in Statamic CMS","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-qcgx-7p5f-hxvr","CVE-2022-24784"],"plain_summary":"OSV carries this publisher advisory for statamic/cms, statamic/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.2.39 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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.2 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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-1a6992895667b610c90d6e0f87ecf08a"],"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":"1.034%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.63858. Missing scores are unknown.","source_id":"sr-1a6992895667b610c90d6e0f87ecf08a"}],"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-402a3bbce429ecfa4e854a6d0b9054e6","url":"https://github.com/advisories/GHSA-qcgx-7p5f-hxvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qcgx-7p5f-hxvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.002Z"},{"id":"sr-1a6992895667b610c90d6e0f87ecf08a","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-2022-24784","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.2.39"]},{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.2"]}],"null_published_at":"2026-10-31T22:27:09.600Z","source_updated_at":"2024-02-16T08:10:37.547Z","source_disclosed_at":"2022-03-29T22:11:45.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:31.002Z"},{"id":"NVI-00003481","kind":"vulnerability","title":"Discoverability of user password hash in Statamic CMS","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-qcgx-7p5f-hxvr","CVE-2022-24784"],"plain_summary":"OSV carries this publisher advisory for statamic/cms, statamic/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.2.39 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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.2 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"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-402a3bbce429ecfa4e854a6d0b9054e6","url":"https://github.com/advisories/GHSA-qcgx-7p5f-hxvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qcgx-7p5f-hxvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.002Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.2.39"]},{"certainty":"source_listed","source_ids":["sr-402a3bbce429ecfa4e854a6d0b9054e6"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"## Description\n\nIt was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.\n\nThe hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.\n\nAdditionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.\n\n## Resolution\n\nFiltering by password or password hash has been disabled.\n\n## Credits\n\nWe would like to thank Thibaud Kehler for reporting the issue.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.2"]}],"null_published_at":"2026-10-31T22:12:48.018Z","source_updated_at":"2024-02-16T08:10:37.547Z","source_disclosed_at":"2022-03-29T22:11:45.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:31.002Z"}],"next_cursor":null,"snapshot_revision":"42594"}