{"answers":{"affected":"2 open source packages ship an affected version, including fuel/core.","exploited":"There is no known exploitation of GHSA-26hp-cgjj-m2j3 in the wild and no public exploit code.","fix":"Upgrade fuel/core to 1.8.0.4 or later.","what":"GHSA-26hp-cgjj-m2j3 is a command injection vulnerability in fuel/core, published on 15 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-26hp-cgjj-m2j3 and fix it if it is affected.\n\nWhat it is: GHSA-26hp-cgjj-m2j3 is a command injection vulnerability in fuel/core, published on 15 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-26hp-cgjj-m2j3 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fuel/core (Packagist): affected all versions; fixed in 1.8.0.4\n- fuel/core (Packagist): affected all versions; fixed in 1.8.0.4\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-26hp-cgjj-m2j3/ (Markdown: https://insights.sbomify.com/GHSA-26hp-cgjj-m2j3/index.md)","id":"GHSA-26hp-cgjj-m2j3","markdown":"https://insights.sbomify.com/GHSA-26hp-cgjj-m2j3/index.md","name":"GHSA-26hp-cgjj-m2j3","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"FuelPHP framework","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary OS commands via crafted image filenames in the FuelPHP ImageMagick driver.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This vulnerability may cause OS commands to be executed when you pass unvalidated image filenames containing specially crafted strings to the ImageMagick driver.","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":"fuel/core ImageMagick driver does not escape all shell arguments.","id":"GHSA-26hp-cgjj-m2j3","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["1.8.0.4"],"introduced":["0"],"last_affected":[],"package":"fuel/core","purl":null,"source":"GHSA-26hp-cgjj-m2j3"},{"ecosystem":"Packagist","fixed":["1.8.0.4"],"introduced":["0"],"last_affected":[],"package":"fuel/core","purl":"pkg:composer/fuel/core","source":"GHSA-26hp-cgjj-m2j3"}],"products":null,"published":"2024-05-15","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 OS commands via crafted image filenames in the FuelPHP ImageMagick driver.","url":"https://insights.sbomify.com/GHSA-26hp-cgjj-m2j3/"}