Silverstripe Assets
Approved changes feed: RSS · Atom
cpe:2.3:a:silverstripe:silverstripe-assets:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Silverstripe (fb3ee4e6-70c4-5017-82a7-81441bb33bd1) |
|---|---|
| Product | Silverstripe Assets (ff039dc1-7113-5b19-b520-fc9e209d7634) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-24749 |
vulnerable | 2026-06-03 15:16:53.130924 |
Silverstripe Assets Module has a DBFile::getURL() permission bypass
MEDIUM (5.3)
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.
Published: 2026-04-16T17:08:59.133Z
Updated: 2026-04-18T02:36:26.887Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.