{"answers":{"affected":"4 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-vgxh-x8jv-hmff in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 4.0.4 or 4.1.1.","what":"GHSA-vgxh-x8jv-hmff is a code injection vulnerability in silverstripe/framework, published on 27 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-vgxh-x8jv-hmff and fix it if it is affected.\n\nWhat it is: GHSA-vgxh-x8jv-hmff is a code injection vulnerability in silverstripe/framework, published on 27 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-vgxh-x8jv-hmff in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 4.0.3-rc1; fixed in 4.0.4\n- silverstripe/framework (Packagist): affected from 4.0.3-rc1; fixed in 4.0.4\n- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.1\n- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.1\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-vgxh-x8jv-hmff/ (Markdown: https://insights.sbomify.com/GHSA-vgxh-x8jv-hmff/index.md)","id":"GHSA-vgxh-x8jv-hmff","markdown":"https://insights.sbomify.com/GHSA-vgxh-x8jv-hmff/index.md","name":"GHSA-vgxh-x8jv-hmff","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"SilverStripe framework","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code if developers pass unsanitized user input to specific template rendering functions in SilverStripe.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"There is a vulnerability whereby arbitrary global functions may be executed if malicious user input is passed through to in the second argument of `ViewableData::renderWith`. This argument resolves associative arrays as template placeholders. This exploit requires that user code has been written which makes use of the second argument in `renderWith` and where user input is passed directly as a value in an associative array without sanitisation such as `Convert::raw2xml()`.\n\n`ViewableData::customise` is not vulnerable.","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/framework code execution vulnerability","id":"GHSA-vgxh-x8jv-hmff","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.0.4"],"introduced":["4.0.3-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-vgxh-x8jv-hmff"},{"ecosystem":"Packagist","fixed":["4.0.4"],"introduced":["4.0.3-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-vgxh-x8jv-hmff"},{"ecosystem":"Packagist","fixed":["4.1.1"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-vgxh-x8jv-hmff"},{"ecosystem":"Packagist","fixed":["4.1.1"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-vgxh-x8jv-hmff"}],"products":null,"published":"2024-05-27","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 execute arbitrary code if developers pass unsanitized user input to specific template rendering functions in SilverStripe.","url":"https://insights.sbomify.com/GHSA-vgxh-x8jv-hmff/"}