in2code/powermail vulnerabilities
Powermail is a well-known, editor-friendly, powerful and easy to use mailform extension for TYPO3 with a lots of features
- Registry
- Composer
- Latest
- 13.3.0
- License
- GPL-2.0-or-later
9 known advisories
The latest version, 13.3.0, is not affected by any of them. Projects on older versions may be.
composer require in2code/powermail:^13.3.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
Security advisories for in2code/powermail
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
powermail TYPO3 extension has Insecure Direct Object Reference
- Affected
- <7.5.1 · >=8.0.0 <8.5.1 · >=9.0.0 <10.9.1 · >=12.0.0 <12.4.1
- Fixed in
- 7.5.1, 8.5.1, 10.9.1, 12.4.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
powermail extension for TYPO3 vulnerable to SQL Injection
- Affected
- <1.5.4
- Fixed in
- 1.5.4
TYPO3 powermail extension has unrestricted file upload vulnerability
- Affected
- <1.6.11 · >=2.0.0 <2.0.14
- Fixed in
- 1.6.11, 2.0.14
TYPO3 powermail extension allows remote attackers to bypass CAPTCHA protection mechanism
- Affected
- >=2.0.0 <2.0.11
- Fixed in
- 2.0.11
powermail extension for TYPO3 has Cross-site Scripting vulnerability
- Affected
- <1.6.5
- Fixed in
- 1.6.5
TYPO3 powermail Extension Vulnerable to SQL Injection via Unspecified Vectors
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Is your in2code/powermail version vulnerable?
- in2code/powermail 13.3No known advisories in 13.3.0
- in2code/powermail 13.2No known advisories in 13.2.1
- in2code/powermail 13.1No known advisories in 13.1.0
- in2code/powermail 13.0No known advisories in 13.0.4
- in2code/powermail 12.6No known advisories in 12.6.1
- in2code/powermail 12.5No known advisories in 12.5.4
- in2code/powermail 12.41 advisory in 12.4.4
- in2code/powermail 12.34 advisories in 12.3.5
- in2code/powermail 12.24 advisories in 12.2.1
- in2code/powermail 12.14 advisories in 12.1.1
- in2code/powermail 11.22 advisories in 11.2.0
- in2code/powermail 11.12 advisories in 11.1.0
- in2code/powermail 11.02 advisories in 11.0.1
Which of your client projects still run an old in2code/powermail?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.