CVE-2019-5715 json
Silverstripe Framework SQLi Vulnerability
published 2019-04-11 7 y ago modified 2026-06-17 4 mo ago also GHSA-wvfw-w3x6-g526 , EUVD-2022-5644
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist silverstripe/framework 3.6.7, 3.7.3, 4.0.7, 4.1.5, 4.2.4, 4.3.1
- silverstripe silverstripe 3.6.7, 3.7.3, 4.0.7, 4.1.5, 4.2.4
Exploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=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 |
3.6.7 4.0.7 3.7.3 4.1.5 4.2.4 4.3.1 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
silverstripe.org
/download/security-releases/ss-2018-021
web, vendor-advisory
-
silverstripe.org
/download/security-releases/
vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-5715
advisory
-
github.com
/silverstripe/silverstripe-framework/issues/8814
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-5715.yaml
web
-
github.com
/silverstripe/silverstripe-framework
package
-
silverstripe.org
/download/security-releases
web
Sources
- CVE List CVE-2019-5715
- GitHub Advisory GHSA-wvfw-w3x6-g526
- NVD CVE-2019-5715
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.