VulertSecurity VulertSecurity

Missing ACL on Reports in silverstripe/framework

silverstripe/framework Updated 02 Oct 2025

Summary

27/05/2024
MODERATE
Yes i
Moderate
4.3

GHSA-52cx-hpc5-cxwc: silverstripe/framework missing ACL on reports. Affects silverstripe/framework across 4 version ranges.

>= 3.1.19-rc1, < 3.1.20 >= 3.2.4-rc1, < 3.2.5 >= 3.3.2-rc1, < 3.3.3 >= 3.4.0-rc1, < 3.4.1

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

A free account is created for continuous monitoring. By scanning, you agree to our Terms & Conditions.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

silverstripe/framework is an open-source PHP framework used for building websites and web applications. It provides a range of features and functionalities to developers, including a reports CMS section. This vulnerability affects versions 3.1.19-rc1 to 3.1.20, 3.2.4-rc1 to 3.2.5, 3.3.2-rc1 to 3.3.3, and 3.4.0-rc1 to 3.4.1 of the framework. The vulnerability allows unauthorized users to view any report in the CMS section, bypassing the access control checks.

Vulnerability Detail

The SS_Report and reports CMS section in silverstripe/framework only checks the canView() function when listing the reports that can be viewed by the current user. However, it fails to perform canView checks when the report is actually viewed. This means that if an unauthorized user knows the URL to a report and can access the Reports section of the CMS, they can view any report, potentially exposing sensitive information.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.1.19-rc1, < 3.1.20 3.1.20 
    composer require silverstripe/framework:3.1.20
  • >= 3.2.4-rc1, < 3.2.5 3.2.5 
    composer require silverstripe/framework:3.2.5
  • >= 3.3.2-rc1, < 3.3.3 3.3.3 
    composer require silverstripe/framework:3.3.3
  • >= 3.4.0-rc1, < 3.4.1 3.4.1 
    composer require silverstripe/framework:3.4.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the latest version of silverstripe/framework.

Conclusion

The missing ACL on reports vulnerability in silverstripe/framework allows unauthorized users to view any report in the CMS section, potentially exposing sensitive information. It is recommended to upgrade to the latest version of silverstripe/framework to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for silverstripe/framework →

Share this vulnerability

FAQ

What is silverstripe/framework?

silverstripe/framework is an open-source PHP framework used for building websites and web applications. It provides a range of features and functionalities to developers.

The reports CMS section in silverstripe/framework allows users to generate and view various reports related to the website or web application.

This vulnerability allows unauthorized users to view any report in the CMS section, potentially exposing sensitive information.

To fix this vulnerability, it is recommended to upgrade to the latest version of silverstripe/framework.

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the latest version of silverstripe/framework.

References

Related vulnerabilities

Recent vulnerabilities recorded for silverstripe/framework.

View all silverstripe/framework vulnerabilities →
Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.1.19-rc1, < 3.1.20 3.1.20 
    composer require silverstripe/framework:3.1.20
  • >= 3.2.4-rc1, < 3.2.5 3.2.5 
    composer require silverstripe/framework:3.2.5
  • >= 3.3.2-rc1, < 3.3.3 3.3.3 
    composer require silverstripe/framework:3.3.3
  • >= 3.4.0-rc1, < 3.4.1 3.4.1 
    composer require silverstripe/framework:3.4.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback