CVE-2026-24749: CWE-863: Incorrect Authorization in silverstripe silverstripe-assets
CVE-2026-24749 is an authorization vulnerability in the Silverstripe Assets Module affecting versions prior to 2. 4. 5 and from 3. 0. 0-rc1 up to 3. 1. 2. The issue causes images accessed via certain methods to incorrectly add an access grant to the current session, bypassing file permissions. This typically occurs when creating image variants using manipulation methods like ScaleWidth() or Convert(). The vulnerability has been fixed in versions 2.
AI Analysis
Technical Summary
The Silverstripe Assets Module, a core component of the Silverstripe Framework, contains an incorrect authorization vulnerability (CWE-863) in versions before 2.4.5 and between 3.0.0-rc1 and 3.1.2. When images are rendered in templates or accessed via DBFile::getURL() or DBFile::getSourceURL(), an access grant is improperly added to the current session, allowing bypass of intended file permissions. This behavior is commonly triggered when creating image variants through manipulation methods such as ScaleWidth() or Convert(). Developers using DBFile directly for DataObject classes not subclassing File and setting file visibility to "protected" must now explicitly provide access grants. The issue is resolved in Silverstripe Assets versions 2.4.5 and 3.1.3.
Potential Impact
The vulnerability allows unauthorized access to files that should be protected by file permissions, potentially exposing sensitive images or assets. The CVSS score of 5.3 (medium severity) reflects a network attack vector with low complexity and no privileges or user interaction required, resulting in limited confidentiality impact without affecting integrity or availability.
Mitigation Recommendations
This vulnerability is fixed in Silverstripe Assets versions 2.4.5 and 3.1.3. Users should upgrade to these or later versions to remediate the issue. Developers who use DBFile directly for DataObject classes with protected visibility must explicitly grant access to those files or change file visibility to "public" if they want default accessibility. Patch status is not explicitly stated in the vendor advisory, but the fix is included in the specified versions.
CVE-2026-24749: CWE-863: Incorrect Authorization in silverstripe silverstripe-assets
Description
CVE-2026-24749 is an authorization vulnerability in the Silverstripe Assets Module affecting versions prior to 2. 4. 5 and from 3. 0. 0-rc1 up to 3. 1. 2. The issue causes images accessed via certain methods to incorrectly add an access grant to the current session, bypassing file permissions. This typically occurs when creating image variants using manipulation methods like ScaleWidth() or Convert(). The vulnerability has been fixed in versions 2.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Silverstripe Assets Module, a core component of the Silverstripe Framework, contains an incorrect authorization vulnerability (CWE-863) in versions before 2.4.5 and between 3.0.0-rc1 and 3.1.2. When images are rendered in templates or accessed via DBFile::getURL() or DBFile::getSourceURL(), an access grant is improperly added to the current session, allowing bypass of intended file permissions. This behavior is commonly triggered when creating image variants through manipulation methods such as ScaleWidth() or Convert(). Developers using DBFile directly for DataObject classes not subclassing File and setting file visibility to "protected" must now explicitly provide access grants. The issue is resolved in Silverstripe Assets versions 2.4.5 and 3.1.3.
Potential Impact
The vulnerability allows unauthorized access to files that should be protected by file permissions, potentially exposing sensitive images or assets. The CVSS score of 5.3 (medium severity) reflects a network attack vector with low complexity and no privileges or user interaction required, resulting in limited confidentiality impact without affecting integrity or availability.
Mitigation Recommendations
This vulnerability is fixed in Silverstripe Assets versions 2.4.5 and 3.1.3. Users should upgrade to these or later versions to remediate the issue. Developers who use DBFile directly for DataObject classes with protected visibility must explicitly grant access to those files or change file visibility to "public" if they want default accessibility. Patch status is not explicitly stated in the vendor advisory, but the fix is included in the specified versions.
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/16/2026, 5:46:58 PM
Last updated: 4/16/2026, 9:15:57 PM
Views: 8
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.