CVE-2022-47408 is a critical-severity (CVSS 9.1) Improper Authentication vulnerability in fixpunkt/fp-newsletter. A fix is available for fixpunkt/fp-newsletter — see the affected versions and patch details below.
Multiple vulnerabilities in extension "Newsletter subscriber management" (fp_newsletter)
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-47408.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
fixpunkt/fp-newsletter🐘fixpunkt/fp-newsletter🐘fixpunkt/fp-newsletterReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The CAPTCHA of the extension can be bypassed which may result in automated creation of various newsletter subscribers. It is possible to provide arbitrary subscription UIDs to the deleteAction of the extension resulting in all newsletter subscribers to be unsubscribed. Insufficient access checks in the createAction and unsubscribeAction can be used to obtain data of existing newsletter subscribers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | fixpunkt/fp-newsletter | ≥ 2.2.0&&< 3.2.6 | 3.2.6composer require fixpunkt/fp-newsletter:^3.2.6 |
| 🐘Packagist | fixpunkt/fp-newsletter | ≥ 2.0.0&&< 2.1.2 | 2.1.2composer require fixpunkt/fp-newsletter:^2.1.2 |
| 🐘Packagist | fixpunkt/fp-newsletter | all versions | 1.1.1composer require fixpunkt/fp-newsletter:^1.1.1 |
Affected Products
fp newsletterfp_newsletter_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fixpunkt/fp-newsletter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fixpunkt/fp-newsletter to 3.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-47408 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2022-47408 in your dependencies?
Find it across Packagist, including transitive dependencies.