dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-24749

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Silverstripe Assets Module versions prior to 2.4.5 and 3.0.0-rc1 through 3.1.2 have a file permission bypass where images accessed via DBFile::getURL() or DBFile::getSourceURL() incorrectly add an access grant to the current session when rendered in templates or during image variant creation (e.g., ScaleWidth(), Convert()).

MitigationUpgrade to Silverstripe Assets Module version 2.4.5 or 3.1.3. Review any custom DataObject classes using DBFile in $db configuration and adjust visibility settings—use 'public' visibility or implement explicit access grants for protected files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Silverstripe Assets Module version
    Check your composer.json or vendor directory for silverstripe/assets version, or run: composer show silverstripe/assets
    Affected if Version is less than 2.4.5, or between 3.0.0-rc1 and 3.1.2 inclusive
  2. Locate custom DataObjects using DBFile
    Search your codebase for $db arrays containing 'DBFile' type declarations, e.g., grep -r '"DBFile"' or grep -r "'DBFile'" in your project directory
    Affected if Any DataObject class defines a DBFile field in $db configuration
  3. Check template usage of getURL or getSourceURL
    Search templates (*.ss files) for calls to $Variable.getURL() or $Variable.getSourceURL() where the variable is a DBFile-backed image
    Affected if Templates invoke getURL() or getSourceURL() on DBFile fields
  4. Check for image variant creation in templates or code
    Search for template calls like $Image.ScaleWidth(), $Image.ScaleHeight(), $Image.Convert(), or corresponding PHP calls to variant creation methods
    Affected if Image variant methods (ScaleWidth, ScaleHeight, Convert, etc.) are called on DBFile image fields in templates or PHP code

Your environment is affected if the Silverstripe Assets Module version falls within the vulnerable range AND DBFile fields are accessed via getURL/getSourceURL in templates or used with image variant methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Silverstripe Assets Module version 2.4.5 or 3.1.3. Review any custom DataObject classes using DBFile in $db configuration and adjust visibility settings—use 'public' visibility or implement explicit access grants for protected files.

Recommended fix Moderate confidence

2.4.5 or 3.1.3

  1. Upgrade Silverstripe Assets Module to version 2.4.5 (for Silverstripe 2.x) or 3.1.3 (for Silverstripe 3.x)
  2. After upgrading, review any DataObject classes that use DBFile directly in $db configuration
  3. If any such files were set to 'protected' visibility, decide whether to: (a) add explicit access grants for those files in your application code, or (b) change visibility to 'public' to maintain default accessibility
  4. Test image rendering operations (ScaleWidth, Convert, etc.) to verify permissions work as expected
  5. Verify that file access permissions are now correctly enforced and not bypassed via session grants
Caveat If you use DBFile in custom DataObjects with 'protected' visibility, you must now explicitly provide access grants or switch to 'public' visibility - files that were accessible by default may require code changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24749 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data