{"answers":{"affected":"6 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-2hpc-mf4q-j885 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 3.1.17, 3.2.2 or 3.3.0.","what":"GHSA-2hpc-mf4q-j885 is a vulnerability in silverstripe/framework, published on 23 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-2hpc-mf4q-j885 and fix it if it is affected.\n\nWhat it is: GHSA-2hpc-mf4q-j885 is a vulnerability in silverstripe/framework, published on 23 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-2hpc-mf4q-j885 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected all versions; fixed in 3.1.17\n- silverstripe/framework (Packagist): affected all versions; fixed in 3.1.17\n- silverstripe/framework (Packagist): affected from 3.2.0; fixed in 3.2.2\n- silverstripe/framework (Packagist): affected from 3.2.0; fixed in 3.2.2\n- silverstripe/framework (Packagist): affected from 3.3.0-beta1; fixed in 3.3.0\n- silverstripe/framework (Packagist): affected from 3.3.0-beta1; fixed in 3.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-2hpc-mf4q-j885/ (Markdown: https://insights.sbomify.com/GHSA-2hpc-mf4q-j885/index.md)","id":"GHSA-2hpc-mf4q-j885","markdown":"https://insights.sbomify.com/GHSA-2hpc-mf4q-j885/index.md","name":"GHSA-2hpc-mf4q-j885","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Silverstripe CMS","requires_auth":"low_privilege","summary":"Attackers can trick CMS users into submitting unauthorized data via CSRF, potentially modifying groups, users, or permissions.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.\n\nThe resolution for this issue is to ensure that all gridFieldAlterAction submissions are checked for the SecurityID token during submission.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Silverstripe CSRF vulnerability in GridFieldAddExistingAutocompleter","id":"GHSA-2hpc-mf4q-j885","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":6,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["3.1.17"],"introduced":["0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-2hpc-mf4q-j885"},{"ecosystem":"Packagist","fixed":["3.1.17"],"introduced":["0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-2hpc-mf4q-j885"},{"ecosystem":"Packagist","fixed":["3.2.2"],"introduced":["3.2.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-2hpc-mf4q-j885"},{"ecosystem":"Packagist","fixed":["3.2.2"],"introduced":["3.2.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-2hpc-mf4q-j885"},{"ecosystem":"Packagist","fixed":["3.3.0"],"introduced":["3.3.0-beta1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-2hpc-mf4q-j885"},{"ecosystem":"Packagist","fixed":["3.3.0"],"introduced":["3.3.0-beta1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-2hpc-mf4q-j885"}],"products":null,"published":"2024-05-23","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can trick CMS users into submitting unauthorized data via CSRF, potentially modifying groups, users, or permissions.","url":"https://insights.sbomify.com/GHSA-2hpc-mf4q-j885/"}