Is in2code/powermail 11.0 vulnerable?
Composer · 2 releases from 11.0.0 to 11.0.1 · latest in2code/powermail is 13.3.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. in2code/powermail 11.0.1, the last 11.0 release, is affected by 2 known security advisories (2 medium), including CVE-2024-45232, CVE-2024-45233. Upgrade to 12.4.0 or later to fix all of them.
composer require in2code/powermail:^12.4.0Is your project on an affected in2code/powermail?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting in2code/powermail 11.0.1
"powermail" (powermail) Insecure Direct Object Reference (IDOR)
- Affected
- >=11.0.0 <12.4.0 · >=9.0.0 <10.9.0 · >=8.0.0 <8.5.0 · <7.5.0
- Fixed in
- 7.5.0, 8.5.0, 10.9.0, 12.4.0
Powermail TYPO3 extension Broken Access Control in the OutputController
- Affected
- <7.5.0 · >=8.0.0 <8.5.0 · >=9.0.0 <10.9.0 · >=11.0.0 <12.4.0
- Fixed in
- 7.5.0, 8.5.0, 10.9.0, 12.4.0
Every in2code/powermail 11.0.x release
Affected: 11.0.0 to 11.0.1. Latest in2code/powermail: 13.3.0.
| Version | Known advisories |
|---|---|
| in2code/powermail 11.0.1 | CVE-2024-45232, CVE-2024-45233 |
| in2code/powermail 11.0.0 | CVE-2024-45232, CVE-2024-45233 |
Which of your client projects are still on in2code/powermail 11.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact in2code/powermail version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other in2code/powermail versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.