CVE-2019-12617 json
SilverStripe Priviledge escalation through cache pollution
published 7y ago modified 4mo ago also GHSA-6r58-4xgr-gm6m , EUVD-2019-0733
- cvss
- 2.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.
Patch / fix
- packagist silverstripe/framework 4.3.5, 4.4.4
Is CVE-2019-12617 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.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=4.4.0, <4.4.4 >=4.3.0, <4.3.5 |
4.4.4 4.3.5 |
References
-
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
-
silverstripe.org
/download/security-releases/CVE-2019-12617
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-12617
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-12617.yaml
web
-
silverstripe.org
/download/security-releases
web
-
silverstripe.org
/download/security-releases/cve-2019-12617
web
Sources
- CVE List CVE-2019-12617
- GitHub Advisory GHSA-6r58-4xgr-gm6m
- NVD CVE-2019-12617
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.