CriticalGHSA-wvfw-w3x6-g526CVE-2019-5715

Silverstripe Framework SQLi Vulnerability

Published 14 May 2022 · Updated 17 Feb 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=3.0.0 <3.6.7
Fixed in: 3.6.7

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.6.7

silverstripe/frameworkComposer

Affected: >=4.0.0 <4.0.7
Fixed in: 4.0.7

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.0.7

silverstripe/frameworkComposer

Affected: >=3.7.0 <3.7.3
Fixed in: 3.7.3

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.7.3

silverstripe/frameworkComposer

Affected: >=4.1.0 <4.1.5
Fixed in: 4.1.5

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.1.5

silverstripe/frameworkComposer

Affected: >=4.2.0 <4.2.4
Fixed in: 4.2.4

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.2.4

silverstripe/frameworkComposer

Affected: >=4.3.0 <4.3.1
Fixed in: 4.3.1

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.3.1

Details

All versions of SilverStripe 3 prior to 3.6.7 and 3.7.3, and all versions of SilverStripe 4 prior to 4.0.7, 4.1.5, 4.2.4, and 4.3.1 allows Reflected SQL Injection through Form and DataObject.

Is GHSA-wvfw-w3x6-g526 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.