CVE-2019-14273 json
Broken access control on files
published 7y ago modified 4mo ago also GHSA-43jj-2rwc-2m3f , EUVD-2020-0534
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
In SilverStripe assets 4.0, there is broken access control on files.
Patch / fix
- packagist silverstripe/framework 4.3.5, 4.4.4
Is CVE-2019-14273 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
1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=4.0.0, <4.3.5 >=4.4.0, <4.4.4 |
4.3.5 4.4.4 |
Classification
- Weakness
-
- CWE-552 Files or Directories Accessible to External Parties
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-14273
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-14273
advisory
-
github.com
/FriendsOfPHP/security-advisories
package
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-14273.yaml
web
-
silverstripe.org
/download/security-releases
web
Sources
- CVE List CVE-2019-14273
- GitHub Advisory GHSA-43jj-2rwc-2m3f
- NVD CVE-2019-14273
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.