# CVE-2022-47411: "Newsletter subscriber management" (fp_newsletter) TYPO3 extension leaks subscriber data

> Attackers can obtain subscriber data via unsubscribe actions in the TYPO3 newsletter extension, requiring an upgrade to fix.

- **Severity:** Critical 9.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-r44w-pfx8-28jv

## What is CVE-2022-47411?

CVE-2022-47411 is a critical vulnerability in n/a, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the fp_newsletter (aka Newsletter subscriber management) extension before 1.1.1, 1.2.0, 2.x before 2.1.2, 2.2.1 through 2.4.0, and 3.x before 3.2.6 for TYPO3. Data about subscribers may be obtained via unsubscribeAction operations.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-47411?

6 open source packages ship an affected version, including fixpunkt/fp-newsletter. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fixpunkt/fp-newsletter` | Packagist | All versions | 1.1.1 |
| `fixpunkt/fp-newsletter` | Packagist | All versions | 1.1.1 |
| `fixpunkt/fp-newsletter` | Packagist | From 1.2.0 | 2.1.2 |
| `fixpunkt/fp-newsletter` | Packagist | From 1.2.0 | 2.1.2 |
| `fixpunkt/fp-newsletter` | Packagist | From 3.0.0 | 3.2.6 |
| `fixpunkt/fp-newsletter` | Packagist | From 3.0.0 | 3.2.6 |

Products: Fp Newsletter Project Fp Newsletter.

## How do I fix CVE-2022-47411?

Upgrade fixpunkt/fp-newsletter to a fixed version for your release line: 1.1.1, 2.1.2 or 3.2.6.

## Is CVE-2022-47411 being exploited?

There is no known exploitation of CVE-2022-47411 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-47408](https://insights.sbomify.com/CVE-2022-47408/): Multiple vulnerabilities in extension "Newsletter subscriber management" (fp_newsletter) (critical 9.1)
- [CVE-2022-47409](https://insights.sbomify.com/CVE-2022-47409/): Missing authorization in n/a (critical 9.1)
- [CVE-2022-47410](https://insights.sbomify.com/CVE-2022-47410/): "Newsletter subscriber management" (fp_newsletter) TYPO3 extension leaks subscriber data (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47411 and fix it if it is affected.

What it is: CVE-2022-47411 is a critical vulnerability in n/a, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47411 in the wild and no public exploit code.

Affected packages and fixed versions:
- fixpunkt/fp-newsletter (Packagist): affected all versions; fixed in 1.1.1
- fixpunkt/fp-newsletter (Packagist): affected all versions; fixed in 1.1.1
- fixpunkt/fp-newsletter (Packagist): affected from 1.2.0; fixed in 2.1.2
- fixpunkt/fp-newsletter (Packagist): affected from 1.2.0; fixed in 2.1.2
- fixpunkt/fp-newsletter (Packagist): affected from 3.0.0; fixed in 3.2.6
- fixpunkt/fp-newsletter (Packagist): affected from 3.0.0; fixed in 3.2.6

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/CVE-2022-47411/ (Markdown: https://insights.sbomify.com/CVE-2022-47411/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-47411
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-47411
- OSV: https://osv.dev/vulnerability/CVE-2022-47411

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-47411/
Summaries are generated and may contain mistakes; the official description above is the record.