NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2019-12245 — framework

MEDIUM

CVE-2019-12245 is a medium-severity (CVSS 5.3) CWE-732 vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Lack of access control on upoaded files

Also known asGHSA-jvx5-rm6q-gx7p
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.62%1.25%1.87%0.3%1.4%May 26Sep 26Oct 26

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/assets🐘silverstripe/assets

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

SilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/frameworkall versions3.6.8composer require silverstripe/framework:^3.6.8
🐘Packagistsilverstripe/framework≥ 3.7.0&&< 3.7.43.7.4composer require silverstripe/framework:^3.7.4
🐘Packagistsilverstripe/framework≥ 4.0.0&&< 4.3.64.3.6composer require silverstripe/framework:^4.3.6
🐘Packagistsilverstripe/framework≥ 4.4.0&&< 4.4.44.4.4composer require silverstripe/framework:^4.4.4
🐘Packagistsilverstripe/assets≥ 1.0.0&&< 1.3.51.3.5composer require silverstripe/assets:^1.3.5
🐘Packagistsilverstripe/assets≥ 1.4.0&&< 1.4.41.4.4composer require silverstripe/assets:^1.4.4

Affected Products

1 product · 1 configurations
Application
silverstripesilverstripe
≤ 4.3.3
range

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

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

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

SilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.
O3 Security · Impact-Aware SCA

Is CVE-2019-12245 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-12245: framework — Fixed in 3.6.8