{"answers":{"affected":"4 open source packages ship an affected version, including silverstripe/assets.","exploited":"There is no known exploitation of CVE-2026-24749 in the wild and no public exploit code.","fix":"Upgrade silverstripe/assets to a fixed version for your release line: 2.4.5 or 3.1.3.","what":"CVE-2026-24749 is a medium-severity missing authorization vulnerability in silverstripe-assets, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24749 and fix it if it is affected.\n\nWhat it is: CVE-2026-24749 is a medium-severity missing authorization vulnerability in silverstripe-assets, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24749 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/assets (Packagist): affected all versions; fixed in 2.4.5\n- silverstripe/assets (Packagist): affected all versions; fixed in 2.4.5\n- silverstripe/assets (Packagist): affected from 3.0.0; fixed in 3.1.3\n- silverstripe/assets (Packagist): affected from 3.0.0; fixed in 3.1.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24749/ (Markdown: https://insights.sbomify.com/CVE-2026-24749/index.md)","id":"CVE-2026-24749","markdown":"https://insights.sbomify.com/CVE-2026-24749/index.md","name":"CVE-2026-24749","record":{"aliases":["GHSA-jgcf-rf45-2f8v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Silverstripe Assets Module","requires_auth":"none","summary":"Attackers can bypass file permissions to access protected assets via DBFile::getURL() in Silverstripe, requiring an upgrade to secure file access controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Silverstripe Assets Module has a DBFile::getURL() permission bypass","id":"CVE-2026-24749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Kiteworks Secure Data Forms vulnerable to Cross-site Scripting","id":"CVE-2026-24750"},"packages":[{"ecosystem":"Packagist","fixed":["2.4.5"],"introduced":["0"],"last_affected":[],"package":"silverstripe/assets","purl":null,"source":"GHSA-jgcf-rf45-2f8v"},{"ecosystem":"Packagist","fixed":["2.4.5"],"introduced":["0"],"last_affected":[],"package":"silverstripe/assets","purl":"pkg:composer/silverstripe/assets","source":"GHSA-jgcf-rf45-2f8v"},{"ecosystem":"Packagist","fixed":["3.1.3"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/assets","purl":null,"source":"GHSA-jgcf-rf45-2f8v"},{"ecosystem":"Packagist","fixed":["3.1.3"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/assets","purl":"pkg:composer/silverstripe/assets","source":"GHSA-jgcf-rf45-2f8v"}],"prev":{"headline":"Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access","id":"CVE-2026-24748"},"products":["silverstripe-assets"],"published":"2026-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-18","vendors":["silverstripe"]},"summary":"Attackers can bypass file permissions to access protected assets via DBFile::getURL() in Silverstripe, requiring an upgrade to secure file access controls.","url":"https://insights.sbomify.com/CVE-2026-24749/"}