What is CVE-2019-16409?

CVE-2019-16409 is a medium-severity security vulnerability in symbiote/silverstripe-versionedfiles (composer), affecting versions <= 2.0.3. It is fixed in 4.3.5, 4.4.4.

How severe is CVE-2019-16409?

CVE-2019-16409 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2019-16409?

symbiote/silverstripe-versionedfiles (composer) versions = 4.0.0, < 4.3.5.

Is there a fix for CVE-2019-16409?

Yes. CVE-2019-16409 is fixed in 4.3.5, 4.4.4. Upgrade to this version or later.

Is CVE-2019-16409 exploitable, and should I be worried?

Whether CVE-2019-16409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-16409 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-16409

Q: How severe is CVE-2019-16409?

CVE-2019-16409 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2019-16409?

symbiote/silverstripe-versionedfiles (composer) versions = 4.0.0, < 4.3.5.

Q: Is there a fix for CVE-2019-16409?

Yes. CVE-2019-16409 is fixed in 4.3.5, 4.4.4. Upgrade to this version or later.

Q: Is CVE-2019-16409 exploitable, and should I be worried?

Whether CVE-2019-16409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-16409 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-16409?

Upgrade: silverstripe/framework to 4.3.5 or later, silverstripe/framework to 4.4.4 or later.

Summary

SilverStripe Versioned Files module Unpublished files are exposed publicly

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

Impact

CVE-2019-16409 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.5, 4.4.4); upgrading removes the vulnerable code path.

Affected versions

symbiote/silverstripe-versionedfiles (<= 2.0.3) silverstripe/framework (>= 4.0.0, < 4.3.5) silverstripe/framework (>= 4.4.0, < 4.4.4)

Security releases

silverstripe/framework → 4.3.5 (composer) silverstripe/framework → 4.4.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

silverstripe/framework to 4.3.5 or later; silverstripe/framework to 4.4.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-16409? CVE-2019-16409 is a medium-severity security vulnerability in symbiote/silverstripe-versionedfiles (composer), affecting versions <= 2.0.3. It is fixed in 4.3.5, 4.4.4.
How severe is CVE-2019-16409? CVE-2019-16409 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2019-16409?
- symbiote/silverstripe-versionedfiles (composer) (versions <= 2.0.3)
- silverstripe/framework (composer) (versions >= 4.0.0, < 4.3.5)
Is there a fix for CVE-2019-16409? Yes. CVE-2019-16409 is fixed in 4.3.5, 4.4.4. Upgrade to this version or later.
Is CVE-2019-16409 exploitable, and should I be worried? Whether CVE-2019-16409 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-16409 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-16409?
- Upgrade silverstripe/framework to 4.3.5 or later
- Upgrade silverstripe/framework to 4.4.4 or later