Vulnerability · Published Apr 16, 2026 · Assigned by GitHub_M

CVE-2026-24749Silverstripe Assets Module has a DBFile::getURL() permission bypass

Medium 5.3

In plain English

A medium-severity incorrect authorization in silverstripe-assets from silverstripe. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 34% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.4%top 65.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

The Silverstripe Assets Module is a required component of Silverstripe Framework. In versions prior to 2.4.5 and 3.0.0-rc1 through 3.1.2, images rendered in templates or otherwise accessed via DBFile::getURL() or DBFile::getSourceURL() incorrectly add an access grant to the current session, which bypasses file permissions. This usually happens when creating an image variant, for example using a manipulation method like ScaleWidth() or Convert(). Note that if developers use DBFile directly in the $db configuration for a DataObject class that doesn't subclass File, and if they were setting the visibility of those files to "protected", those files will now need an explicit access grant to be accessed. If developers do not want to explicitly provide access grants for these files in their apps (i.e. they want these files to be accessible by default), they should use the "public" visibility. This issue has been fixed in versions 2.4.5 and 3.1.3.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Packagistsilverstripe/assets2.4.5GHSA-jgcf-rf45-2f8v
Packagistsilverstripe/assets3.1.3GHSA-jgcf-rf45-2f8v

Affected products (as reported)

VendorProductVersions
silverstripe silverstripe-assets < 2.4.5>= 3.0.0-rc1, < 3.1.3

Weakness: CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References