# GHSA-26hq-7286-mg8f: Magento Patch SUPEE-9652 - Remote Code Execution using mail vulnerability

> Remote attackers can execute arbitrary code on Magento 1 installations using sendmail with specific non-default configurations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-26hq-7286-mg8f?

GHSA-26hq-7286-mg8f is a command injection vulnerability in magento/community-edition, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zend Framework 1 vulnerability can be remotely exploited to execute code in Magento 1. While the issue is not reproducible in Magento 2, the library code is the same so it was fixed as well.

Note: while the vulnerability is scored as critical, few systems are affected. To be affected by the vulnerability the installation has to:

- use sendmail as the mail transport agent

- have specific, non-default configuration settings as described [here](https://magento.com/security/patches/supee-9652#:~:text=settings%20as%20described-,here,-.).

## Which versions are affected by GHSA-26hq-7286-mg8f?

2 open source packages ship an affected version, including magento/community-edition.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `magento/community-edition` | Packagist | From 1.9.0.0 | 1.14.3.2 |
| `magento/community-edition` | Packagist | From 1.9.0.0 | 1.14.3.2 |

## How do I fix GHSA-26hq-7286-mg8f?

Upgrade magento/community-edition to 1.14.3.2 or later.

## Is GHSA-26hq-7286-mg8f being exploited?

There is no known exploitation of GHSA-26hq-7286-mg8f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-26hq-7286-mg8f and fix it if it is affected.

What it is: GHSA-26hq-7286-mg8f is a command injection vulnerability in magento/community-edition, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-26hq-7286-mg8f in the wild and no public exploit code.

Affected packages and fixed versions:
- magento/community-edition (Packagist): affected from 1.9.0.0; fixed in 1.14.3.2
- magento/community-edition (Packagist): affected from 1.9.0.0; fixed in 1.14.3.2

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-26hq-7286-mg8f/ (Markdown: https://insights.sbomify.com/GHSA-26hq-7286-mg8f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-26hq-7286-mg8f

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