CVE-2019-12246 json
SilverStripe Denial of Service on flush and development URL tools
published 6y ago modified 4mo ago also GHSA-5fr8-xhqq-4p3q , EUVD-2022-2576
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
SilverStripe through 4.3.3 allows a Denial of Service on flush and development URL tools.
Patch / fix
- packagist silverstripe/framework 4.4.0
Is CVE-2019-12246 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=4.0.0, <4.4.0 <=3.6 |
4.4.0 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/silverstripe/silverstripe-framework/commit/ca56e8d78e468874b9267c94d8ec75240b6da0ab
web
-
silverstripe.org
/download/security-releases/
vendor-advisory
-
silverstripe.org
/blog/tag/release
web, release-notes, vendor-advisory
-
forum.silverstripe.org
/c/releases
web, release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-12246
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-12246.yaml
web
-
github.com
/silverstripe/silverstripe-framework
package
-
silverstripe.org
/download/security-releases/cve-2019-12246
web
Sources
- CVE List CVE-2019-12246
- GitHub Advisory GHSA-5fr8-xhqq-4p3q
- NVD CVE-2019-12246
Fencer Intel 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.