CVE-2019-16409
MEDIUMCVE-2019-16409 is a medium-severity (CVSS 5.3) vulnerability in symbiote/silverstripe-versionedfiles. O3 Security confirms whether CVE-2019-16409 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
SilverStripe Versioned Files module Unpublished files are exposed publicly
Real-World Exposure
symbiote/silverstripe-versionedfiles🐘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
In the Versioned Files module through 2.0.3 for SilverStripe 3.x, unpublished versions of files are publicly exposed to anyone who can guess their URL. This guess could be highly informed by a basic understanding of the symbiote/silverstripe-versionedfiles source code. (Users who upgrade from SilverStripe 3.x to 4.x and had Versioned Files installed have no further need for this module, because the 4.x release has built-in versioning. However, nothing in the upgrade process automates the destruction of these insecure artefacts, nor alerts the user to the criticality of destruction.)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symbiote/silverstripe-versionedfiles | all versions | No fix |
| 🐘Packagist | silverstripe/framework | ≥ 4.0.0&&< 4.3.5 | 4.3.5 |
| 🐘Packagist | silverstripe/framework | ≥ 4.4.0&&< 4.4.4 | 4.4.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symbiote/silverstripe-versionedfiles. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of symbiote/silverstripe-versionedfiles has shipped for CVE-2019-16409 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-16409 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2019-16409. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-16409 in your dependencies?
O3 detects CVE-2019-16409 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.