How severe is CVE-2019-5715?

CVE-2019-5715 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-5715?

CVE-2019-5715 affects the following packages: silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-5715?

Update silverstripe/framework to 3.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-5715 is resolved across your whole dependency graph.

How do I detect CVE-2019-5715 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-5715 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2019-5715 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-5715 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-5715?

CVE-2019-5715 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-5715?

CVE-2019-5715 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-5715 published, and has it been updated?

CVE-2019-5715 was published on April 11, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2019-5715 — framework

CRITICAL

CVE-2019-5715 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Silverstripe Framework SQLi Vulnerability

Also known asGHSA-wvfw-w3x6-g526

Published

Apr 11, 2019

Updated

Oct 24, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/framework`	≥ 3.0.0&&< 3.6.7	3.6.7`composer require silverstripe/framework:^3.6.7`
🐘Packagist	`silverstripe/framework`	≥ 4.0.0&&< 4.0.7	4.0.7`composer require silverstripe/framework:^4.0.7`
🐘Packagist	`silverstripe/framework`	≥ 3.7.0&&< 3.7.3	3.7.3`composer require silverstripe/framework:^3.7.3`
🐘Packagist	`silverstripe/framework`	≥ 4.1.0&&< 4.1.5	4.1.5`composer require silverstripe/framework:^4.1.5`
🐘Packagist	`silverstripe/framework`	≥ 4.2.0&&< 4.2.4	4.2.4`composer require silverstripe/framework:^4.2.4`
🐘Packagist	`silverstripe/framework`	≥ 4.3.0&&< 4.3.1	4.3.1`composer require silverstripe/framework:^4.3.1`

Affected Products

1 product · 6 configurations

Application

silverstripesilverstripe

≥ 4.2.0 && < 4.2.4

1 version

4.3.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/framework to 3.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-5715 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2019-5715 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

silverstripe-framework

4.5/10

Code-Review4/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

Disclosed

Apr 11, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-5715

GHSA-wvfw-w3x6-g526

References

Advisorysilverstripe.org · security releases Advisorysilverstripe.org · ss 2018 021 Advisorynvd.nist.gov · CVE 2019 5715 Webgithub.com Webgithub.com · CVE 2019 5715.yaml Websilverstripe.org · security releases Packagegithub.com · silverstripe framework

Related vulnerabilities

This CVE is critical severity — higher than any of the other 8 CVEs affecting silverstripe/framework (highest there: moderate).

CVE-2026-54720GHSA-256q-hx8w-xcqxCVE-2025-30148GHSA-74j9-xhqr-6qv3CVE-2024-47605CVE-2024-53277GHSA-mqf3-qpc3-g26qGHSA-52cw-pvq9-9m5v

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-5715 — framework

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-5715 in your dependencies?