Is silverstripe/framework 4.10 vulnerable?
Composer · 12 releases from 4.10.0 to 4.10.11 · latest silverstripe/framework is 6.3.1 · checked 1 Nov 2026
Yes: 17 known advisories
Yes. silverstripe/framework 4.10.11, the last 4.10 release, is affected by 17 known security advisories (14 medium, 3 low), including CVE-2026-54720, CVE-2025-30148, CVE-2024-53277. 5 more affect earlier 4.10.x releases. Upgrade to 6.2.2 or later to fix all of them.
composer require silverstripe/framework:^6.2.2Advisories affecting silverstripe/framework 4.10.11
Silverstripe Framework: Possible XSS attack through media embed
- Affected
- <6.2.2
- Fixed in
- 6.2.2
Silverstripe Framework user enumeration via timing attack on login and password reset forms
- Affected
- >=4.0.0 <5.3.23
- Fixed in
- 5.3.23
Silverstripe Framework has a XSS vulnerability in HTML editor
- Affected
- <5.3.23
- Fixed in
- 5.3.23
Reflected Cross Site Scripting (XSS) in error message
- Affected
- <5.3.8
- Fixed in
- 5.3.8
Silverstripe Framework has a Reflected Cross Site Scripting (XSS) in error message
- Affected
- <5.3.8
- Fixed in
- 5.3.8
Silverstripe Framework has a XSS in form messages
- Affected
- <5.3.8
- Fixed in
- 5.3.8
Silverstripe Framework has a XSS via insert media remote file oembed
- Affected
- <5.3.8
- Fixed in
- 5.3.8
Silverstripe uses TinyMCE which allows svg files linked in object tags
- Affected
- <5.2.16
- Fixed in
- 5.2.16
Silverstripe Framework has a Cross-site Scripting vulnerability with encoded payload
- Affected
- <5.2.16
- Fixed in
- 5.2.16
Record titles for restricted records can be viewed if exposed by GridFieldAddExistingAutocompleter
- Affected
- <4.13.39 · >=5.0.0 <5.1.11
- Fixed in
- 4.13.39, 5.1.11
Silverstripe Framework: Members with no password can be created and bypass custom login forms
- Affected
- >=3.0.0 <4.13.14 · >=5.0.0 <5.0.13
- Fixed in
- 4.13.14, 5.0.13
Missing permission check of canView in GridFieldPrintButton
- Affected
- <4.12.5
- Fixed in
- 4.12.5
Open redirect vulnerability on CMSSecurity relogin screen
- Affected
- <4.12.5
- Fixed in
- 4.12.5
Reflected XSS in querystring parameters
- Affected
- >=4.0.0 <4.11.13
- Fixed in
- 4.11.13
Stored XSS using HTMLEditor
- Affected
- >=4.0.0 <4.11.13
- Fixed in
- 4.11.13
Stored XSS using uppercase characters in HTMLEditor
- Affected
- >=4.0.0 <4.11.13
- Fixed in
- 4.11.13
Silverstripe XSS in shortcodes
- Affected
- >=4.0.0 <4.11.13
- Fixed in
- 4.11.13
Fixed within 4.10.x, affecting earlier releases
Blind SQL Injection via GridFieldSortableHeader
- Affected
- >=4.0.0 <4.10.11 · >=4.11.0 <4.11.14
- Fixed in
- 4.10.11, 4.11.14
Quadratic blowup in Convert::xml2array()
- Affected
- >=4.0.0 <4.10.9
- Fixed in
- 4.10.9
Stored XSS via HTML fields in SilverStripe Framework
- Affected
- >=4.0.0 <4.10.9
- Fixed in
- 4.10.9
Stored XSS in link tags added via XHR in SilverStripe Framework
- Affected
- >=4.0.0 <4.10.9
- Fixed in
- 4.10.9
Business Logic Errors in SilverStripe Framework
- Affected
- <4.10.1
- Fixed in
- 4.10.1
Which of your client projects are still on silverstripe/framework 4.10?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact silverstripe/framework version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other silverstripe/framework versions
- silverstripe/framework 4.13
- silverstripe/framework 4.12
- silverstripe/framework 4.11
- silverstripe/framework 4.9
- silverstripe/framework 4.8
- silverstripe/framework 4.7
- silverstripe/framework 6.3
- silverstripe/framework 6.2
- silverstripe/framework 6.1
- silverstripe/framework 6.0
- silverstripe/framework 5.4
- silverstripe/framework 5.3
- All silverstripe/framework advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.