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

Medium 5.3 Published Updated

Attackers can bypass file permissions to access protected assets via DBFile::getURL() in Silverstripe, requiring an upgrade to secure file access controls.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-24749?

CVE-2026-24749 is a medium-severity missing authorization vulnerability in silverstripe-assets, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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.

Weakness: CWE-863

Which versions are affected by CVE-2026-24749?

4 open source packages ship an affected version, including silverstripe/assets.

PackageAffectedFixed in
silverstripe/assets PackagistAll versions2.4.5
silverstripe/assets PackagistAll versions2.4.5
silverstripe/assets PackagistFrom 3.0.03.1.3
silverstripe/assets PackagistFrom 3.0.03.1.3

How do I fix CVE-2026-24749?

Upgrade silverstripe/assets to a fixed version for your release line: 2.4.5 or 3.1.3.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-24749 being exploited?

There is no known exploitation of CVE-2026-24749 in the wild and no public exploit code.

Sources

Also known as GHSA-jgcf-rf45-2f8v.

Is CVE-2026-24749 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free