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-vcg6-8fxc-x5cqhigh8.8

silverstripe/framework allows upload of dangerous file types

No CVE assignedCheck your stack

The advisory, in context

Some potentially dangerous file types exist in File.allowed_extensions which could allow a malicious CMS user to upload files that then get executed in the security context of the website. We have removed the ability to upload .css, .js, .potm, .dotm, .xltm and .jar files in the default configuration. Since allowed_extensions are synced to webserver configuration (in assets/.htaccess) automatically, this will also deny access to any existing uploads with these extensions.

Review our security guidelines for the Common Web Platform and the File Security guide for SilverStripe 4 to find out how to add or remove extensions.

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

From 3.6.5-rc1 before 3.6.6

Fixed in 3.6.6

2 explicitly affected versions

3.6.5, 3.6.6-rc1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.6.5-rc1"
        },
        {
          "fixed": "3.6.6"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.6.5",
    "3.6.6-rc1"
  ]
}
Ecosystem versions

From 4.0.3-rc1 before 4.0.4

Fixed in 4.0.4

1 explicitly affected versions

4.0.3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "4.0.3-rc1"
        },
        {
          "fixed": "4.0.4"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "4.0.3"
  ]
}
Ecosystem versions

From 4.1.0-rc1 before 4.1.1

Fixed in 4.1.1

3 explicitly affected versions

4.1.0, 4.1.0-rc1, 4.1.0-rc2

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "4.1.0-rc1"
        },
        {
          "fixed": "4.1.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "4.1.0",
    "4.1.0-rc1",
    "4.1.0-rc2"
  ]
}

References