CVE-2019-12246 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.
SilverStripe Denial of Service on flush and development URL tools
EPSS Exploitation Probability
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
silverstripe/framework🐘silverstripe/frameworkReal-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
SilverStripe through 4.3.3 allows a Denial of Service on flush and development URL tools.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/framework | ≥ 4.0.0&&< 4.4.0 | 4.4.0composer require silverstripe/framework:^4.4.0 |
| 🐘Packagist | silverstripe/framework | all versions | No fix |
Affected Products
silverstripesilverstripeDetection & mitigation playbook
Open-source dependencyDetect
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 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12246 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2019-12246 in your dependencies?
Find it across Packagist, including transitive dependencies.