Silverstripe Assets Module has a DBFile::getURL() permission bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-24749: 0.40% estimated exploitation activity in the next 30 days; percentile 34.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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 you use DBFile directly in the $db configuration for a DataObject class that doesn't subclass File, and if you were setting the visibility of those files to "protected", those files will now need an explicit access grant to be accessed. If you do not want to explicitly provide access grants for these files (i.e. you want these files to be accessible by default), you should use the "public" visibility. Reported by Restruct web & apps

Published by the source

16 Apr 2026, 20:40 UTC

Last modified by the source

27 Apr 2026, 14:20 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jgcf-rf45-2f8v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24749

Advisory: Silverstripe Assets Module has a DBFile::getURL() permission bypass
IDs: CVE-2026-24749, GHSA-jgcf-rf45-2f8v
Record: https://patchnext.com/advisories/cve-2026-24749 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: silverstripe/assets 3.1.3, 2.4.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist silverstripe/assets: affected < 2.4.5; >= 3.0.0, < 3.1.3; fixed in 2.4.5, 3.1.3

## Suggested inspection (read-only)
- Packagist silverstripe/assets: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on silverstripe/assets.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jgcf-rf45-2f8v (GitHub-reviewed advisory GHSA-jgcf-rf45-2f8v lists affected ranges: Packagist silverstripe/assets >=0 =3.0.0 <3.1.3)

Commands are suggestions: review each one before running it.