GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
GHSA-xm6j-x342-gwq9medium5.3

SilverStripe Versioned Files module Unpublished files are exposed publicly

Check your stack

The advisory, in context

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

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

Earlier releases through 2.0.3 (inclusive)

No fix recorded for this interval.

17 explicitly affected versions

1.0.1, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 2.0.0, 2.0.1, 2.0.2, 2.0.3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "last_affected": "2.0.3"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.0.1",
    "1.0.10",
    "1.0.11",
    "1.0.12",
    "1.0.13",
    "1.0.2",
    "1.0.3",
    "1.0.4",
    "1.0.5",
    "1.0.6",
    "1.0.7",
    "1.0.8",
    "1.0.9",
    "2.0.0",
    "2.0.1",
    "2.0.2",
    "2.0.3"
  ]
}
Ecosystem versions

From 4.0.0 before 4.3.5

Fixed in 4.3.5

30 explicitly affected versions

4.0.0, 4.0.1, 4.0.1-rc1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.1.0, 4.1.0-rc1, 4.1.0-rc2, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.2.0, 4.2.0-beta1, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, 4.3.0, 4.3.0-rc1, 4.3.1, 4.3.2, 4.3.3, 4.3.4

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "4.0.0"
        },
        {
          "fixed": "4.3.5"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "4.0.0",
    "4.0.1",
    "4.0.1-rc1",
    "4.0.2",
    "4.0.3",
    "4.0.4",
    "4.0.5",
    "4.0.6",
    "4.0.7",
    "4.1.0",
    "4.1.0-rc1",
    "4.1.0-rc2",
    "4.1.1",
    "4.1.2",
    "4.1.3",
    "4.1.4",
    "4.1.5",
    "4.2.0",
    "4.2.0-beta1",
    "4.2.1",
    "4.2.2",
    "4.2.3",
    "4.2.4",
    "4.2.5",
    "4.3.0",
    "4.3.0-rc1",
    "4.3.1",
    "4.3.2",
    "4.3.3",
    "4.3.4"
  ]
}
Ecosystem versions

From 4.4.0 before 4.4.4

Fixed in 4.4.4

4 explicitly affected versions

4.4.0, 4.4.1, 4.4.2, 4.4.3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "4.4.0"
        },
        {
          "fixed": "4.4.4"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "4.4.0",
    "4.4.1",
    "4.4.2",
    "4.4.3"
  ]
}

References