GHSA-97jm-g33h-f46g: silverstripe/framework ReadOnly transformation for formfields exploitable
Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeFieldReadonly. 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.
Published May 23, 2024
Affected packages
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- < 3.1.21
- Fixed in
- 3.1.21
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.2.0, < 3.2.6
- Fixed in
- 3.2.6
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.3.0, < 3.3.4
- Fixed in
- 3.3.4
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.4.0, < 3.4.2
- Fixed in
- 3.4.2
- Check
composer show silverstripe/framework
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
SilverStripe 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.
Readonly 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.
References
- https://github.com/silverstripe/silverstripe-framework/commit/8336cb96b9600dacafa8a525c92662345b52cfae
- https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-010-1.yaml
- https://www.silverstripe.org/download/security-releases/ss-2016-010
- https://github.com/advisories/GHSA-97jm-g33h-f46g
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-88987
Silverstripe Framework: XSS via XHTML data URI
medium5.4Nov 16, 2026CVE-2026-88988
Silverstripe Framework: XSS via SVG data URI
medium5.4Nov 16, 2026CVE-2026-88989
Silverstripe Framework: Auth bypass GridFieldDetailForm
medium4.3Nov 16, 2026CVE-2026-91112
Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation
medium6.8Nov 16, 2026CVE-2026-91113
Silverstripe Framework: User-controlled ClassName allows unauthorized record type change
medium4.3Nov 16, 2026CVE-2026-91115
Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter
high8.8Nov 16, 2026
