# GHSA-6mgp-v5cm-ghg5: Drupal core Remote Code Execution

> An attacker can execute arbitrary code on the server by exploiting unsanitized shell arguments in Drupal's email system.

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

## What is GHSA-6mgp-v5cm-ghg5?

GHSA-6mgp-v5cm-ghg5 is a command injection vulnerability in drupal/core, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Drupal core, when sending email some variables were not being sanitized for shell arguments in `DefaultMailSystem::mail()`, which could lead to remote code execution.

## Which versions are affected by GHSA-6mgp-v5cm-ghg5?

6 open source packages ship an affected version, including drupal/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 7.0 | 7.60 |
| `drupal/core` | Packagist | From 7.0 | 7.60 |
| `drupal/core` | Packagist | From 8.0.0 | 8.5.8 |
| `drupal/core` | Packagist | From 8.0.0 | 8.5.8 |
| `drupal/core` | Packagist | From 8.6.0 | 8.6.2 |
| `drupal/core` | Packagist | From 8.6.0 | 8.6.2 |

## How do I fix GHSA-6mgp-v5cm-ghg5?

Upgrade drupal/core to a fixed version for your release line: 7.60, 8.5.8 or 8.6.2.

## Is GHSA-6mgp-v5cm-ghg5 being exploited?

There is no known exploitation of GHSA-6mgp-v5cm-ghg5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6mgp-v5cm-ghg5 and fix it if it is affected.

What it is: GHSA-6mgp-v5cm-ghg5 is a command injection vulnerability in drupal/core, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-6mgp-v5cm-ghg5 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 7.0; fixed in 7.60
- drupal/core (Packagist): affected from 7.0; fixed in 7.60
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.5.8
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.5.8
- drupal/core (Packagist): affected from 8.6.0; fixed in 8.6.2
- drupal/core (Packagist): affected from 8.6.0; fixed in 8.6.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-6mgp-v5cm-ghg5/ (Markdown: https://insights.sbomify.com/GHSA-6mgp-v5cm-ghg5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6mgp-v5cm-ghg5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6mgp-v5cm-ghg5/
Summaries are generated and may contain mistakes; the official description above is the record.