{"items":[{"id":"NVI-00005189","kind":"vulnerability","title":"Silverstripe Framework: Members with no password can be created and bypass custom login forms","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":"disputed","identifiers":["GHSA-36xx-7vf6-7mv3","CVE-2023-32302"],"plain_summary":"OSV carries this publisher advisory for silverstripe/framework, silverstripe/framework. 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.13.14 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"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.0.13 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"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-a06f7c177e9d5de795030b24fa760b91"],"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":[],"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-85ff35af5eb4fc27d32fbf662bf22d78","url":"https://github.com/advisories/GHSA-36xx-7vf6-7mv3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-36xx-7vf6-7mv3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.651Z"},{"id":"sr-a06f7c177e9d5de795030b24fa760b91","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-32302","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-32302","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:36.867Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have some `Member` records in your system already which have empty passwords. To detect these, you can loop over all `Member` records with `Member::get()` and pass each record into the below method. It might be sensible to create a `BuildTask` for this purpose.\n  ```php\n    private function memberHasBlankPassword(Member $member): bool\n    {\n        // skip default admin as this is created programatically\n        if ($member->isDefaultAdmin()) {\n            return false;\n        }\n      ","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 4.13.14"]},{"certainty":"source_listed","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have some `Member` records in your system already which have empty passwords. To detect these, you can loop over all `Member` records with `Member::get()` and pass each record into the below method. It might be sensible to create a `BuildTask` for this purpose.\n  ```php\n    private function memberHasBlankPassword(Member $member): bool\n    {\n        // skip default admin as this is created programatically\n        if ($member->isDefaultAdmin()) {\n            return false;\n        }\n      ","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.13"]}],"null_published_at":"2026-11-06T15:18:11.520Z","source_updated_at":"2024-02-16T08:21:44.979Z","source_disclosed_at":"2023-07-31T22:00:58.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:49.651Z"},{"id":"NVI-00005189","kind":"vulnerability","title":"Silverstripe Framework: Members with no password can be created and bypass custom login forms","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-36xx-7vf6-7mv3","CVE-2023-32302"],"plain_summary":"OSV carries this publisher advisory for silverstripe/framework, silverstripe/framework. 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.13.14 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"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.0.13 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"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-85ff35af5eb4fc27d32fbf662bf22d78","url":"https://github.com/advisories/GHSA-36xx-7vf6-7mv3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-36xx-7vf6-7mv3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.651Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have some `Member` records in your system already which have empty passwords. To detect these, you can loop over all `Member` records with `Member::get()` and pass each record into the below method. It might be sensible to create a `BuildTask` for this purpose.\n  ```php\n    private function memberHasBlankPassword(Member $member): bool\n    {\n        // skip default admin as this is created programatically\n        if ($member->isDefaultAdmin()) {\n            return false;\n        }\n      ","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 4.13.14"]},{"certainty":"source_listed","source_ids":["sr-85ff35af5eb4fc27d32fbf662bf22d78"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have some `Member` records in your system already which have empty passwords. To detect these, you can loop over all `Member` records with `Member::get()` and pass each record into the below method. It might be sensible to create a `BuildTask` for this purpose.\n  ```php\n    private function memberHasBlankPassword(Member $member): bool\n    {\n        // skip default admin as this is created programatically\n        if ($member->isDefaultAdmin()) {\n            return false;\n        }\n      ","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.13"]}],"null_published_at":"2026-10-31T22:13:01.453Z","source_updated_at":"2024-02-16T08:21:44.979Z","source_disclosed_at":"2023-07-31T22:00:58.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:49.651Z"}],"next_cursor":null,"snapshot_revision":"42594"}