CVE-2026-24749: CWE-863: Incorrect Authorization in silverstripe silverstripe-assets
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.
AI Analysis
Technical Summary
The Silverstripe Assets Module, a core component of the Silverstripe Framework, contains an authorization flaw in certain versions where image access via DBFile::getURL() or DBFile::getSourceURL() improperly grants access rights to the current session. This bypasses intended file permission controls, especially when image variants are generated through manipulation methods like ScaleWidth() or Convert(). Developers using DBFile directly for DataObject classes not subclassing File and setting file visibility to "protected" must now explicitly grant access. The issue is resolved in versions 2.4.5 and 3.1.3.
Potential Impact
This vulnerability allows unauthorized access to protected image files by bypassing file permission checks, potentially exposing sensitive media content. The CVSS score of 5.3 indicates a medium severity impact with confidentiality loss but no impact on integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix is available in Silverstripe Assets Module versions 2.4.5 and 3.1.3. Users should upgrade to these or later versions to remediate the vulnerability. Developers who use DBFile directly with protected visibility files must explicitly grant access or set file visibility to "public" if they want files accessible by default.
CVE-2026-24749: CWE-863: Incorrect Authorization in silverstripe silverstripe-assets
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.
CVSS v3.1
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Silverstripe Assets Module, a core component of the Silverstripe Framework, contains an authorization flaw in certain versions where image access via DBFile::getURL() or DBFile::getSourceURL() improperly grants access rights to the current session. This bypasses intended file permission controls, especially when image variants are generated through manipulation methods like ScaleWidth() or Convert(). Developers using DBFile directly for DataObject classes not subclassing File and setting file visibility to "protected" must now explicitly grant access. The issue is resolved in versions 2.4.5 and 3.1.3.
Potential Impact
This vulnerability allows unauthorized access to protected image files by bypassing file permission checks, potentially exposing sensitive media content. The CVSS score of 5.3 indicates a medium severity impact with confidentiality loss but no impact on integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix is available in Silverstripe Assets Module versions 2.4.5 and 3.1.3. Users should upgrade to these or later versions to remediate the vulnerability. Developers who use DBFile directly with protected visibility files must explicitly grant access or set file visibility to "public" if they want files accessible by default.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-26T19:06:16.060Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e11d0782d89c981fabdc64
Added to database: 4/16/2026, 5:31:51 PM
Last enriched: 4/24/2026, 4:12:08 PM
Last updated: 6/2/2026, 4:27:35 AM
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.