{"answers":{"affected":"4 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-f43j-8hq4-2xj9 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-f43j-8hq4-2xj9 is a 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-f43j-8hq4-2xj9 and fix it if it is affected.\n\nWhat it is: GHSA-f43j-8hq4-2xj9 is a 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-f43j-8hq4-2xj9 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.4\n- silverstripe/framework (Packagist): affected from 4.0.0-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-f43j-8hq4-2xj9/ (Markdown: https://insights.sbomify.com/GHSA-f43j-8hq4-2xj9/index.md)","id":"GHSA-f43j-8hq4-2xj9","markdown":"https://insights.sbomify.com/GHSA-f43j-8hq4-2xj9/index.md","name":"GHSA-f43j-8hq4-2xj9","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"low_privilege","summary":"Attackers can execute uploaded PHP scripts in the assets directory via crafted URLs, leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"A weakness in the .htaccess rules preventing requests to uploaded PHP scripts allows PHP scripts that had made their way into the assets directory to be successfully executed through the use of a specially crafted URL. There are protections in place to disallow upload of PHP scripts through the CMS, meaning this weakness does not lead to direct vulnerabilities.\n\nIn addition, sites hosted on the New Zealand Common Web Platform or SilverStripe Platform have additional configuration in place which prevents PHP script execution in assets, even in a malicious party manages to upload these into the folder.","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 uploaded PHP script execution in assets","id":"GHSA-f43j-8hq4-2xj9","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.0.4"],"introduced":["4.0.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-f43j-8hq4-2xj9"},{"ecosystem":"Packagist","fixed":["4.0.4"],"introduced":["4.0.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-f43j-8hq4-2xj9"},{"ecosystem":"Packagist","fixed":["4.1.1"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-f43j-8hq4-2xj9"},{"ecosystem":"Packagist","fixed":["4.1.1"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-f43j-8hq4-2xj9"}],"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 uploaded PHP scripts in the assets directory via crafted URLs, leading to remote code execution.","url":"https://insights.sbomify.com/GHSA-f43j-8hq4-2xj9/"}