In Silverstripe Assets Module versions before 2.4.5 and prior to 3.1.3, the method that generates URLs for database files does not respect the file’s visibility setting when creating image variants. As a result, the system creates an implicit session grant that allows any user to download the file, even when the file is marked as "protected". This flaw maps to CWE-863, indicating a breach of access control. The consequence is that sensitive files can be accessed by unauthorized users, undermining confidentiality and potentially enabling further exploitation if the files contain privileged data.

Any installation of the Silverstripe Framework that includes the Assets Module with a version earlier than 2.4.5 or between 3.0.0‑rc1 and 3.1.2 is vulnerable. The issue manifests when templates render images or when image manipulation functions such as ScaleWidth() or Convert() are called. Systems that define DBFile fields in custom DataObject classes without subclassing File and set their visibility to "protected" are also at risk, since the implicit grant can expose those files as well.

The CVSS base score of 5.3 categorizes the issue as medium severity. No EPSS score is provided, and the vulnerability is not listed in the CISA KEV catalog, indicating that there is no known widespread exploitation. However, because the flaw is triggered by common image processing operations that occur during normal site operation, an attacker who can influence image manipulation requests—such as through crafted URLs or template injection—could easily cause the system to grant unauthorized access to protected files. The lack of explicit access controls on indirectly accessed files or database fields further lowers the barrier to exploitation.