Is silverstripe/framework 4.3 vulnerable?
Composer · 6 releases from 4.3.0 to 4.3.5 · latest silverstripe/framework is 6.3.2 · checked 2 Nov 2026
Yes: 30 known advisories
Yes. silverstripe/framework 4.3.5, the last 4.3 release, is affected by 30 known security advisories (3 high, 24 medium, 3 low), including CVE-2022-38148, CVE-2020-6164, CVE-2020-9280. 8 more affect earlier 4.3.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.3.5
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
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
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
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
SilverStripe XXE Vulnerability in CSSContentParser
- Affected
- >=4.0.0 <4.7.4
- Fixed in
- 4.7.4
Silverstripe CMS information disclosure
- Affected
- >=4.0.0 <4.4.7 · >=4.5.0 <4.5.4
- Fixed in
- 4.4.7, 4.5.4
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 Folders migrated from 3.x may be unsafe to upload to
- Affected
- >=4.0.0 <4.4.6
- Fixed in
- 4.4.6
SilverStripe Denial of Service on flush and development URL tools
- Affected
- >=4.0.0 <4.4.0 · <=3.6
- Fixed in
- 4.4.0
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
Reflected XSS in SilverStripe
- Affected
- >=4.5.0 <4.5.2 · >=4.0.0 <4.4.5
- Fixed in
- 4.4.5, 4.5.2
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 4.3.x, affecting earlier releases
SilverStripe asset-admin Cross-site Scripting (XSS)
- Affected
- >=4.0.0 <4.3.5 · >=4.4.0 <4.4.4
- Fixed in
- 4.3.5, 4.4.4
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
Broken access control on files
- Affected
- >=4.0.0 <4.3.5 · >=4.4.0 <4.4.4
- Fixed in
- 4.3.5, 4.4.4
SilverStripe Priviledge escalation through cache pollution
- Affected
- >=4.4.0 <4.4.4 · >=4.3.0 <4.3.5
- Fixed in
- 4.3.5, 4.4.4
Session fixation in change password form
- Affected
- >=3.7.0 <3.7.4 · >=4.4.0 <4.4.4 · >=3.6.0 <3.6.8 · >=4.0.0 <4.3.5
- Fixed in
- 3.6.8, 3.7.4, 4.3.5, 4.4.4
Missing warning can lead to unauthenticated admin access in SilverStripe
- Affected
- >=4.1.0 <4.3.5
- Fixed in
- 4.3.5
SilverStripe Versioned Files module Unpublished files are exposed publicly
- Affected
- >=4.0.0 <4.3.5 · >=4.4.0 <4.4.4
- Fixed in
- 4.3.5, 4.4.4
Which of your client projects are still on silverstripe/framework 4.3?
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.6
- silverstripe/framework 4.5
- silverstripe/framework 4.4
- silverstripe/framework 4.2
- silverstripe/framework 4.1
- silverstripe/framework 4.0
- 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.