GHSA-52CX-HPC5-CXWC

silverstripe/framework missing ACL on reports

The SS_Report, and the reports CMS section only checks canView() when listing the reports that can be viewed by the current user.

It does not (and should) perform canView checks when the report is actually viewed, so if you know the URL to a report and can otherwise access the Reports section of the CMS, you can view any report.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

GHSA-52CX-HPC5-CXWC has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.20, 3.2.5, 3.3.3, 3.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-52CX-HPC5-CXWC? GHSA-52CX-HPC5-CXWC is a medium-severity missing authorization vulnerability in silverstripe/framework (composer), affecting versions >= 3.1.19-rc1, < 3.1.20. It is fixed in 3.1.20, 3.2.5, 3.3.3, 3.4.1. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is GHSA-52CX-HPC5-CXWC? GHSA-52CX-HPC5-CXWC has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of silverstripe/framework are affected by GHSA-52CX-HPC5-CXWC? silverstripe/framework (composer) versions >= 3.1.19-rc1, < 3.1.20 is affected.
4. Is there a fix for GHSA-52CX-HPC5-CXWC? Yes. GHSA-52CX-HPC5-CXWC is fixed in 3.1.20, 3.2.5, 3.3.3, 3.4.1. Upgrade to this version or later.
5. Is GHSA-52CX-HPC5-CXWC exploitable, and should I be worried? Whether GHSA-52CX-HPC5-CXWC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-52CX-HPC5-CXWC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-52CX-HPC5-CXWC?
   • Upgrade silverstripe/framework to 3.1.20 or later
   • Upgrade silverstripe/framework to 3.2.5 or later
   • Upgrade silverstripe/framework to 3.3.3 or later
   • Upgrade silverstripe/framework to 3.4.1 or later

Other vulnerabilities in silverstripe/framework