CVE-2026-24749

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-24749", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-01-26T19:06:16.060Z", "datePublished": "2026-04-16T17:08:59.133Z", "dateUpdated": "2026-04-18T02:36:26.887Z"}, "containers": {"cna": {"title": "Silverstripe Assets Module has a DBFile::getURL() permission bypass", "problemTypes": [{"descriptions": [{"cweId": "CWE-863", "lang": "en", "description": "CWE-863: Incorrect Authorization", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/silverstripe/silverstripe-assets/security/advisories/GHSA-jgcf-rf45-2f8v", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/silverstripe/silverstripe-assets/security/advisories/GHSA-jgcf-rf45-2f8v"}, {"name": "https://www.silverstripe.org/download/security-releases/cve-2026-24749", "tags": ["x_refsource_MISC"], "url": "https://www.silverstripe.org/download/security-releases/cve-2026-24749"}], "affected": [{"vendor": "silverstripe", "product": "silverstripe-assets", "versions": [{"version": "< 2.4.5", "status": "affected"}, {"version": ">= 3.0.0-rc1, < 3.1.3", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-04-16T17:08:59.133Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-jgcf-rf45-2f8v", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-04-18T02:35:55.902112Z", "id": "CVE-2026-24749", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-04-18T02:36:26.887Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-24749", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-04-18T02:35:55.902112Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-04-18T02:36:22.003Z"}}], "cna": {"title": "Silverstripe Assets Module has a DBFile::getURL() permission bypass", "source": {"advisory": "GHSA-jgcf-rf45-2f8v", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}}], "affected": [{"vendor": "silverstripe", "product": "silverstripe-assets", "versions": [{"status": "affected", "version": "< 2.4.5"}, {"status": "affected", "version": ">= 3.0.0-rc1, < 3.1.3"}]}], "references": [{"url": "https://github.com/silverstripe/silverstripe-assets/security/advisories/GHSA-jgcf-rf45-2f8v", "name": "https://github.com/silverstripe/silverstripe-assets/security/advisories/GHSA-jgcf-rf45-2f8v", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://www.silverstripe.org/download/security-releases/cve-2026-24749", "name": "https://www.silverstripe.org/download/security-releases/cve-2026-24749", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-863", "description": "CWE-863: Incorrect Authorization"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-04-16T17:08:59.133Z"}}}, "cveMetadata": {"cveId": "CVE-2026-24749", "state": "PUBLISHED", "dateUpdated": "2026-04-18T02:36:26.887Z", "dateReserved": "2026-01-26T19:06:16.060Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-04-16T17:08:59.133Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "silverstripe-assets", "vendor": "silverstripe", "versions": [{"status": "affected", "version": "< 2.4.5"}, {"status": "affected", "version": ">= 3.0.0-rc1, < 3.1.3"}]}], "source": "security-advisories@github.com"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "El M\u00f3dulo de Activos de Silverstripe es un componente requerido de Silverstripe framework. En versiones anteriores a la 2.4.5 y de la 3.0.0-rc1 a la 3.1.2, las im\u00e1genes renderizadas en plantillas o accedidas de otra manera a trav\u00e9s de DBFile::getURL() o DBFile::getSourceURL() a\u00f1aden incorrectamente una concesi\u00f3n de acceso a la sesi\u00f3n actual, lo que elude los permisos de archivo. Esto suele ocurrir al crear una variante de imagen, por ejemplo, usando un m\u00e9todo de manipulaci\u00f3n como ScaleWidth() o Convert(). Tenga en cuenta que si los desarrolladores usan DBFile directamente en la configuraci\u00f3n $db para una clase DataObject que no subclase File, y si estaban configurando la visibilidad de esos archivos como \u2019protected\u2019, esos archivos ahora necesitar\u00e1n una concesi\u00f3n de acceso expl\u00edcita para ser accedidos. Si los desarrolladores no quieren proporcionar expl\u00edcitamente concesiones de acceso para estos archivos en sus aplicaciones (es decir, quieren que estos archivos sean accesibles por defecto), deber\u00edan usar la visibilidad \u2019public\u2019. Este problema ha sido solucionado en las versiones 2.4.5 y 3.1.3."}], "id": "CVE-2026-24749", "lastModified": "2026-10-26T21:10:00.170", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 1.4, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-24749", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-04-18T02:35:55.902112Z", "version": "2.0.3"}}]}, "published": "2026-04-16T18:16:44.610", "references": [{"source": "security-advisories@github.com", "url": "https://github.com/silverstripe/silverstripe-assets/security/advisories/GHSA-jgcf-rf45-2f8v"}, {"source": "security-advisories@github.com", "url": "https://www.silverstripe.org/download/security-releases/cve-2026-24749"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Deferred", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-863"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,2.4.5)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[3.0.0-rc1,3.1.3)"}}], "enrichment": {"confidence": 88.0, "confidence_source": "matching", "scores": [{"score": 88.0, "source": "matching"}]}, "original": {"product": "silverstripe-assets", "source": "cna", "vendor": "silverstripe"}, "product": "silverstripe", "vendor": "silverstripe"}], "analysis": {"en": {"generated_at": "2026-04-16T18:29:48.715348+00:00", "value": {"mitigation_remediation": ["Upgrade Silverstripe Assets Module to version 2.4.5 or newer, or to 3.1.3 or newer, to eliminate the implicit grant behavior.", "If an upgrade cannot be performed immediately, change the visibility of all DBFile objects to \"public\" so that files are accessible by default and no implicit grants are created.", "For legacy DBFile usage in custom DataObject classes, either convert those fields to subclass File or explicitly grant access to protected files; do not rely on the default grant mechanism."], "summary": {"action": "Patch Upgrade", "impact": "Permission Bypass"}, "threat_synthesis": {"affected_systems": "Any installation of the Silverstripe Framework that includes the Assets Module with a version earlier than 2.4.5 or between 3.0.0\u2011rc1 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.", "description_and_impact": "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\u2019s 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.", "risk_and_exploitability": "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\u2014such as through crafted URLs or template injection\u2014could 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."}}}}, "created": "2026-04-16T18:30:10.539249+00:00", "updated": "2026-04-16T18:58:23.631566+00:00", "vendors": ["silverstripe", "silverstripe$PRODUCT$silverstripe"]}