Is silverstripe/framework 3.5 vulnerable?
Composer · 9 releases from 3.5.0 to 3.5.8 · latest silverstripe/framework is 6.3.1 · checked 1 Nov 2026
Yes: 21 known advisories
Yes. silverstripe/framework 3.5.8, the last 3.5 release, is affected by 21 known security advisories (1 critical, 16 medium, 4 low), including CVE-2019-5715, CVE-2026-54720, CVE-2025-30148. 11 more affect earlier 3.5.x releases. Upgrade to 6.2.2 or later to fix all of them.
composer require silverstripe/framework:^6.2.2Advisories affecting silverstripe/framework 3.5.8
Silverstripe Framework: Possible XSS attack through media embed
- Affected
- <6.2.2
- Fixed in
- 6.2.2
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
silverstripe/framework sends passwords back to browsers under some circumstances
- Affected
- >=3.5.5-rc1 <3.7.0 · >=4.0.3-rc1 <4.0.4 · >=4.1.0-rc1 <4.1.1
- Fixed in
- 3.7.0, 4.0.4, 4.1.1
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
Silverstripe CMS XSS Vulnerability
- Affected
- >=3.0.0 <3.7.5
- Fixed in
- 3.7.5
SilverStripe Web Cache Poisoning through HTTPRequestBuilder
- Affected
- >=4.0.0 <4.4.7 · >=4.5.0 <4.5.4 · >=3.0.0 <3.7.5
- Fixed in
- 3.7.5, 4.4.7, 4.5.4
SilverStripe Denial of Service on flush and development URL tools
- Affected
- >=4.0.0 <4.4.0 · <=3.6
- Fixed in
- 4.4.0
Silverstripe Flash Clipboard Reflected XSS
- Affected
- >=3.0.0 <4.3.5 · >=4.4.0-rc1 <4.4.4
- Fixed in
- 4.3.5, 4.4.4
Silverstripe Framework SQLi Vulnerability
- Affected
- >=3.0.0 <3.6.7 · >=4.0.0 <4.0.7 · >=3.7.0 <3.7.3 · >=4.1.0 <4.1.5 · >=4.2.0 <4.2.4 · >=4.3.0 <4.3.1
- Fixed in
- 3.6.7, 3.7.3, 4.0.7, 4.1.5, 4.2.4, 4.3.1
FormField with square brackets in field name skips validation
- Affected
- >=3.0.0 <4.7.4
- Fixed in
- 4.7.4
Business Logic Errors in SilverStripe Framework
- Affected
- <4.10.1
- Fixed in
- 4.10.1
Lack of access control on upoaded files
- Affected
- <3.6.8 · >=3.7.0 <3.7.4 · >=4.0.0 <4.3.6 · >=4.4.0 <4.4.4
- Fixed in
- 3.6.8, 3.7.4, 4.3.6, 4.4.4
Fixed within 3.5.x, affecting earlier releases
silverstripe/framework Privilege Escalation Risk in Member Edit form
- Affected
- >=3.5.7-rc1 <3.5.8 · >=3.6.0-rc1 <3.6.6 · >=4.0.0-rc1 <4.0.4 · >=4.1.0-rc1 <4.1.1
- Fixed in
- 3.5.8, 3.6.6, 4.0.4, 4.1.1
silverstripe/framework SQL injection in full text search
- Affected
- >=3.5.0-rc1 <3.5.6 · >=3.6.0-rc1 <3.6.3 · >=4.0.0-rc1 <4.0.1
- Fixed in
- 3.5.6, 3.6.3, 4.0.1
silverstripe/framework users inadvertently passing sensitive data to LoginAttempt
- Affected
- >=3.5.0-rc1 <3.5.6 · >=3.6.0-rc1 <3.6.3 · >=4.0.0-rc1 <4.0.1
- Fixed in
- 3.5.6, 3.6.3, 4.0.1
silverstripe/framework CSV Excel Macro Injection
- Affected
- >=3.5.0-rc1 <3.5.6 · >=3.6.0-rc1 <3.6.3 · >=4.0.0-rc1 <4.0.1
- Fixed in
- 3.5.6, 3.6.3, 4.0.1
silverstripe/framework vulnerable to user enumeration via timing attack on login and password reset forms
- Affected
- >=3.5.0-rc1 <3.5.5 · >=3.6.0-rc1 <3.6.2
- Fixed in
- 3.5.5, 3.6.2
silverstripe/framework's User-Agent header not correctly invalidating user session
- Affected
- >=3.5.0-rc1 <3.5.6 · >=3.6.0-rc1 <3.6.3
- Fixed in
- 3.5.6, 3.6.3
silverstripe/framework has Cross-site Scripting vulnerability in page history comparison
- Affected
- >=3.4.0-rc1 <3.4.6 · >=3.5.0-rc1 <3.5.4
- Fixed in
- 3.4.6, 3.5.4
silverstripe/framework has Cross-site Scripting vulnerability in RedirectorPage
- Affected
- >=3.4.0-rc1 <3.4.6 · >=3.5.0-rc1 <3.5.4
- Fixed in
- 3.4.6, 3.5.4
silverstripe/framework has Cross-site Scripting vulnerability in page name
- Affected
- >=3.4.0-rc1 <3.4.4 · >=3.5.0-rc1 <3.5.2
- Fixed in
- 3.4.4, 3.5.2
silverstripe/framework member disclosure in login form
- Affected
- >=3.4.0-rc1 <3.4.6 · >=3.5.0-rc1 <3.5.4
- Fixed in
- 3.4.6, 3.5.4
SilverStripe CSV Excel Macro Injection
- Affected
- <3.5.6 · >=3.6.0 <3.6.3 · >=4.0.0 <4.0.1
- Fixed in
- 3.5.6, 3.6.3, 4.0.1
Which of your client projects are still on silverstripe/framework 3.5?
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.0
- silverstripe/framework 3.7
- silverstripe/framework 3.6
- silverstripe/framework 3.4
- silverstripe/framework 3.3
- silverstripe/framework 3.2
- 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.