# GHSA-26hp-cgjj-m2j3: fuel/core ImageMagick driver does not escape all shell arguments.

> Attackers can execute arbitrary OS commands via crafted image filenames in the FuelPHP ImageMagick driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-26hp-cgjj-m2j3?

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.

### Official description

This vulnerability may cause OS commands to be executed when you pass unvalidated image filenames containing specially crafted strings to the ImageMagick driver.

## Which versions are affected by GHSA-26hp-cgjj-m2j3?

2 open source packages ship an affected version, including fuel/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuel/core` | Packagist | All versions | 1.8.0.4 |
| `fuel/core` | Packagist | All versions | 1.8.0.4 |

## How do I fix GHSA-26hp-cgjj-m2j3?

Upgrade fuel/core to 1.8.0.4 or later.

## Is GHSA-26hp-cgjj-m2j3 being exploited?

There is no known exploitation of GHSA-26hp-cgjj-m2j3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-26hp-cgjj-m2j3 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of GHSA-26hp-cgjj-m2j3 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuel/core (Packagist): affected all versions; fixed in 1.8.0.4
- fuel/core (Packagist): affected all versions; fixed in 1.8.0.4

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-26hp-cgjj-m2j3/ (Markdown: https://insights.sbomify.com/GHSA-26hp-cgjj-m2j3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-26hp-cgjj-m2j3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-26hp-cgjj-m2j3/
Summaries are generated and may contain mistakes; the official description above is the record.