{"items":[{"id":"NVI-00004629","kind":"vulnerability","title":"silverstripe/framework ReadOnly transformation for formfields exploitable","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-97jm-g33h-f46g"],"plain_summary":"OSV carries this publisher advisory for silverstripe/framework, silverstripe/framework, 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 3.1.21 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"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.2.6 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"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.4 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"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.4.2 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"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-6d838765a6bd202147955e71e4c6e8e6","url":"https://github.com/advisories/GHSA-97jm-g33h-f46g","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-97jm-g33h-f46g","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.682Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeField_Readonly. Values submitted to through these form fields are not filtered out from the form session data, and might be shown to the user depending on the form behaviour. For example, form validation errors cause the form to re-render with previously submitted values by default.\n\nSilverStripe forms automatically load values from request data (GET and POST), which enables malicious use of URLs if your form uses these fields and doesn't overwrite data on form construction.\n\nReadonly and disabled form fields are already filtered out in Form->saveInto(), so maliciously submitted data on these fields doesn't make it into the database unless you are accessing form values directly in your saving logic.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.1.21"]},{"certainty":"source_listed","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeField_Readonly. Values submitted to through these form fields are not filtered out from the form session data, and might be shown to the user depending on the form behaviour. For example, form validation errors cause the form to re-render with previously submitted values by default.\n\nSilverStripe forms automatically load values from request data (GET and POST), which enables malicious use of URLs if your form uses these fields and doesn't overwrite data on form construction.\n\nReadonly and disabled form fields are already filtered out in Form->saveInto(), so maliciously submitted data on these fields doesn't make it into the database unless you are accessing form values directly in your saving logic.","public_affected_ranges":["ECOSYSTEM: introduced 3.2.0; fixed 3.2.6"]},{"certainty":"source_listed","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeField_Readonly. Values submitted to through these form fields are not filtered out from the form session data, and might be shown to the user depending on the form behaviour. For example, form validation errors cause the form to re-render with previously submitted values by default.\n\nSilverStripe forms automatically load values from request data (GET and POST), which enables malicious use of URLs if your form uses these fields and doesn't overwrite data on form construction.\n\nReadonly and disabled form fields are already filtered out in Form->saveInto(), so maliciously submitted data on these fields doesn't make it into the database unless you are accessing form values directly in your saving logic.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.4"]},{"certainty":"source_listed","source_ids":["sr-6d838765a6bd202147955e71e4c6e8e6"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeField_Readonly. Values submitted to through these form fields are not filtered out from the form session data, and might be shown to the user depending on the form behaviour. For example, form validation errors cause the form to re-render with previously submitted values by default.\n\nSilverStripe forms automatically load values from request data (GET and POST), which enables malicious use of URLs if your form uses these fields and doesn't overwrite data on form construction.\n\nReadonly and disabled form fields are already filtered out in Form->saveInto(), so maliciously submitted data on these fields doesn't make it into the database unless you are accessing form values directly in your saving logic.","public_affected_ranges":["ECOSYSTEM: introduced 3.4.0; fixed 3.4.2"]}],"null_published_at":"2026-10-31T22:12:57.135Z","source_updated_at":"2024-11-28T05:30:39.149Z","source_disclosed_at":"2024-05-23T19:50:27.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:10.682Z"}],"next_cursor":null,"snapshot_revision":"42594"}