{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/graphql.","exploited":"There is no known exploitation of GHSA-wjg9-v8cf-f5q2 in the wild and no public exploit code.","fix":"Upgrade silverstripe/graphql to 2.0.3 or later.","what":"GHSA-wjg9-v8cf-f5q2 is a vulnerability in silverstripe/graphql, published on 28 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-wjg9-v8cf-f5q2 and fix it if it is affected.\n\nWhat it is: GHSA-wjg9-v8cf-f5q2 is a vulnerability in silverstripe/graphql, published on 28 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-wjg9-v8cf-f5q2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/graphql (Packagist): affected from 2.0.0; fixed in 2.0.3\n- silverstripe/graphql (Packagist): affected from 2.0.0; fixed in 2.0.3\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-wjg9-v8cf-f5q2/ (Markdown: https://insights.sbomify.com/GHSA-wjg9-v8cf-f5q2/index.md)","id":"GHSA-wjg9-v8cf-f5q2","markdown":"https://insights.sbomify.com/GHSA-wjg9-v8cf-f5q2/index.md","name":"GHSA-wjg9-v8cf-f5q2","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe GraphQL module","requires_auth":"low_privilege","summary":"Authenticated users can be tricked into executing unauthorized data mutations or deletions via CSRF in the SilverStripe GraphQL controller.","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":"The GraphQL controller lacked any CSRF protection, meaning authenticated users could be forced or tricked into visiting a URL that would send a GET request to the affected web server that could mutate or destroy data without the user knowing.","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/graphql Cross-Site Request Forgery vulnerability","id":"GHSA-wjg9-v8cf-f5q2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.0.3"],"introduced":["2.0.0"],"last_affected":[],"package":"silverstripe/graphql","purl":null,"source":"GHSA-wjg9-v8cf-f5q2"},{"ecosystem":"Packagist","fixed":["2.0.3"],"introduced":["2.0.0"],"last_affected":[],"package":"silverstripe/graphql","purl":"pkg:composer/silverstripe/graphql","source":"GHSA-wjg9-v8cf-f5q2"}],"products":null,"published":"2024-05-28","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":"Authenticated users can be tricked into executing unauthorized data mutations or deletions via CSRF in the SilverStripe GraphQL controller.","url":"https://insights.sbomify.com/GHSA-wjg9-v8cf-f5q2/"}