# GHSA-g4pf-3jvq-2gcw: TYPO3 Remote Code Execution in third party library swiftmailer

> Remote code execution vulnerability in the swiftmailer library used by TYPO3 allows attackers to execute arbitrary code.

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

## What is GHSA-g4pf-3jvq-2gcw?

GHSA-g4pf-3jvq-2gcw is a code injection vulnerability in typo3/cms, published on 5 Jun 2024. It can be exploited over the network.

### Official description

TYPO3 uses the package swiftmailer/swiftmailer for mail actions. This package is known to be vulnerable to Remote Code Execution.

## Which versions are affected by GHSA-g4pf-3jvq-2gcw?

6 open source packages ship an affected version, including typo3/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.30 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.30 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.15 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.15 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.5.1 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.5.1 |

## How do I fix GHSA-g4pf-3jvq-2gcw?

Upgrade typo3/cms to a fixed version for your release line: 6.2.30, 7.6.15 or 8.5.1.

## Is GHSA-g4pf-3jvq-2gcw being exploited?

There is no known exploitation of GHSA-g4pf-3jvq-2gcw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g4pf-3jvq-2gcw and fix it if it is affected.

What it is: GHSA-g4pf-3jvq-2gcw is a code injection vulnerability in typo3/cms, published on 5 Jun 2024. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-g4pf-3jvq-2gcw in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.30
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.30
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.15
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.15
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.5.1
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.5.1

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-g4pf-3jvq-2gcw/ (Markdown: https://insights.sbomify.com/GHSA-g4pf-3jvq-2gcw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g4pf-3jvq-2gcw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g4pf-3jvq-2gcw/
Summaries are generated and may contain mistakes; the official description above is the record.