SilverStripe Versioned Files module Unpublished files are exposed publicly

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2019-16409: 1.20% estimated exploitation activity in the next 30 days; percentile 68.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

12 Nov 2019, 23:01 UTC

Last modified by the source

7 Feb 2024, 18:26 UTC

Source last checked

26 Oct 2026, 14:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xm6j-x342-gwq9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-16409

Advisory: SilverStripe Versioned Files module Unpublished files are exposed publicly
IDs: CVE-2019-16409, GHSA-xm6j-x342-gwq9
Record: https://patchnext.com/advisories/cve-2019-16409 (revision 1, source checked 26 Oct 2026, 14:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: silverstripe/framework 4.4.4, 4.3.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist symbiote/silverstripe-versionedfiles: affected <= 2.0.3
- Packagist silverstripe/framework: affected >= 4.0.0, < 4.3.5; >= 4.4.0, < 4.4.4; fixed in 4.4.4, 4.3.5

## Suggested inspection (read-only)
- Packagist symbiote/silverstripe-versionedfiles: check the installed version with your package manager.
- Packagist silverstripe/framework: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on symbiote/silverstripe-versionedfiles, silverstripe/framework.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xm6j-x342-gwq9 (GitHub-reviewed advisory GHSA-xm6j-x342-gwq9 lists affected ranges: Packagist symbiote/silverstripe-versionedfiles >=0 =4.0.0 =4.4.0 <4.4.4)

Commands are suggestions: review each one before running it.