GHSA-2HPC-MF4Q-J885

Silverstripe CSRF vulnerability in GridFieldAddExistingAutocompleter

GridField does not have sufficient CSRF protection, meaning that in some cases users with CMS access can be tricked into posting unspecified data into the CMS from external websites. Amongst other default CMS interfaces, GridField is used for management of groups, users and permissions in the CMS.

The resolution for this issue is to ensure that all gridFieldAlterAction submissions are checked for the SecurityID token during submission.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

GHSA-2HPC-MF4Q-J885 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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.17, 3.2.2, 3.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-2HPC-MF4Q-J885? GHSA-2HPC-MF4Q-J885 is a medium-severity cross-site request forgery (CSRF) vulnerability in silverstripe/framework (composer), affecting versions <= 3.1.16. It is fixed in 3.1.17, 3.2.2, 3.3.0. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is GHSA-2HPC-MF4Q-J885? GHSA-2HPC-MF4Q-J885 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-2HPC-MF4Q-J885? silverstripe/framework (composer) versions <= 3.1.16 is affected.
4. Is there a fix for GHSA-2HPC-MF4Q-J885? Yes. GHSA-2HPC-MF4Q-J885 is fixed in 3.1.17, 3.2.2, 3.3.0. Upgrade to this version or later.
5. Is GHSA-2HPC-MF4Q-J885 exploitable, and should I be worried? Whether GHSA-2HPC-MF4Q-J885 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-2HPC-MF4Q-J885 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-2HPC-MF4Q-J885?
   • Upgrade silverstripe/framework to 3.1.17 or later
   • Upgrade silverstripe/framework to 3.2.2 or later
   • Upgrade silverstripe/framework to 3.3.0 or later

Other vulnerabilities in silverstripe/framework