Is in2code/powermail 12.5 vulnerable?
Composer · 5 releases from 12.5.0 to 12.5.4 · latest in2code/powermail is 13.3.0 · checked 18 Nov 2026
No known advisories in the last release
in2code/powermail 12.5.4, the last 12.5 release, has no known advisories. 1 advisory affects earlier 12.5.x releases, so update to 12.5.4.
composer require in2code/powermail:^12.5.4Is 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
Fixed within 12.5.x, affecting earlier releases
Powermail extension for TYPO3 allows Insecure Direct Object Reference
- Affected
- >=12.0.0 <12.5.3 · >=13.0.0 <13.0.1
- Fixed in
- 12.5.3, 13.0.1
Every in2code/powermail 12.5.x release
Affected: 12.5.0 to 12.5.2. 12.5.3 and later are not affected. Latest in2code/powermail: 13.3.0.
| Version | Known advisories |
|---|---|
| in2code/powermail 12.5.4 | None |
| in2code/powermail 12.5.3 | None |
| in2code/powermail 12.5.2 | CVE-2025-7899 |
| in2code/powermail 12.5.1 | CVE-2025-7899 |
| in2code/powermail 12.5.0 | CVE-2025-7899 |
Which of your client projects are still on in2code/powermail 12.5?
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.