Is silverstripe/framework 3.0 vulnerable?
Composer · 13 releases from 3.0.2 to 3.0.14 · latest silverstripe/framework is 6.3.2 · checked 2 Nov 2026
Yes: 30 known advisories
Yes. silverstripe/framework 3.0.14, the last 3.0 release, is affected by 30 known security advisories (1 critical, 26 medium, 3 low), including CVE-2019-5715, CVE-2026-54720, CVE-2025-30148. 4 more affect earlier 3.0.x releases. At least one has no fixed release yet.
Advisories affecting silverstripe/framework 3.0.14
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 ReadOnly transformation for formfields exploitable
- Affected
- <3.1.21 · >=3.2.0 <3.2.6 · >=3.3.0 <3.3.4 · >=3.4.0 <3.4.2
- Fixed in
- 3.1.21, 3.2.6, 3.3.4, 3.4.2
Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers
- Affected
- <3.1.17 · >=3.2.0 <3.2.2 · >=3.3.0-beta1 <3.3.0
- Fixed in
- 3.1.17, 3.2.2, 3.3.0
Silverstripe CSRF vulnerability in GridFieldAddExistingAutocompleter
- Affected
- <3.1.17 · >=3.2.0 <3.2.2 · >=3.3.0-beta1 <3.3.0
- Fixed in
- 3.1.17, 3.2.2, 3.3.0
Silverstripe Missing security check on dev/build/defaults
- Affected
- <3.1.17 · >=3.2.0 <3.2.2 · >=3.3.0-beta1 <3.3.0
- Fixed in
- 3.1.17, 3.2.2, 3.3.0
Silverstripe HtmlEditor embed url sanitisation
- Affected
- >=3.0.0 <3.2.1
- Fixed in
- 3.2.1
Silverstripe Form field validation message XSS vulnerability
- Affected
- >=3.0.0 <3.1.16 · >=3.2.0 <3.2.1
- Fixed in
- 3.1.16, 3.2.1
Silverstripe XSS in dev/build returnURL Parameter
- Affected
- <3.1.14
- Fixed in
- 3.1.14
SilverStripe framework XML Quadratic Blowup Attack
- Affected
- <3.1.12
- Fixed in
- 3.1.12
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 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
Silverstripe CMS Open Redirect
- Affected
- <=3.1.13
- Fixed in
- No fix released
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.0.x, affecting earlier releases
SilverStripe Vulnerability on 'isDev', 'isTest' and 'flush' $_GET validation
- Affected
- >=3.0.0 <3.0.14 · >=3.1.0 <3.1.13
- Fixed in
- 3.0.14, 3.1.13
Silverstripe External redirection risk in Security?ReturnURL
- Affected
- <3.0.14 · >=3.1.0 <3.1.13
- Fixed in
- 3.0.14, 3.1.13
Silverstripe XSS In rewritten hash links
- Affected
- <3.0.13 · >=3.1.0 <3.1.12
- Fixed in
- 3.0.13, 3.1.12
Silverstripe IE requests not properly behaving with rewritehashlinks
- Affected
- <3.0.13 · >=3.1.0 <3.1.12
- Fixed in
- 3.0.13, 3.1.12
Which of your client projects are still on silverstripe/framework 3.0?
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 3.3
- silverstripe/framework 3.2
- silverstripe/framework 3.1
- silverstripe/framework 2.5
- silverstripe/framework 2.4
- silverstripe/framework 6.3
- silverstripe/framework 6.2
- silverstripe/framework 6.1
- silverstripe/framework 6.0
- silverstripe/framework 5.4
- silverstripe/framework 5.3
- silverstripe/framework 5.2
- 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.