# CVE-2026-24749: Silverstripe Assets Module has a DBFile::getURL() permission bypass

> Attackers can bypass file permissions to access protected assets via DBFile::getURL() in Silverstripe, requiring an upgrade to secure file access controls.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2026
- **Updated:** 18 Apr 2026
- **Also known as:** GHSA-jgcf-rf45-2f8v

## What is CVE-2026-24749?

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.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-24749?

4 open source packages ship an affected version, including silverstripe/assets.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/assets` | Packagist | All versions | 2.4.5 |
| `silverstripe/assets` | Packagist | All versions | 2.4.5 |
| `silverstripe/assets` | Packagist | From 3.0.0 | 3.1.3 |
| `silverstripe/assets` | Packagist | From 3.0.0 | 3.1.3 |

## How do I fix CVE-2026-24749?

Upgrade silverstripe/assets to a fixed version for your release line: 2.4.5 or 3.1.3.

## Is CVE-2026-24749 being exploited?

There is no known exploitation of CVE-2026-24749 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24749 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-24749 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/assets (Packagist): affected all versions; fixed in 2.4.5
- silverstripe/assets (Packagist): affected all versions; fixed in 2.4.5
- silverstripe/assets (Packagist): affected from 3.0.0; fixed in 3.1.3
- silverstripe/assets (Packagist): affected from 3.0.0; fixed in 3.1.3

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24749/ (Markdown: https://insights.sbomify.com/CVE-2026-24749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24749
- OSV: https://osv.dev/vulnerability/CVE-2026-24749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24749/
Summaries are generated and may contain mistakes; the official description above is the record.