Vulnerability Database · Packagist · Package report

in2code/powermail: vulnerability history, versions and safety

in2code/powermail is a package in the Packagist ecosystem. Vulert records 9 vulnerabilities for it across 92 releases, from May 2022 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H3 M5 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on in2code/powermail i

Updated on 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 22 Jul 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 9 vulnerabilities on record across 3 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 3 years · 0 in the last year i
  • Latest disclosure 22 Jul 2025 i
  • Highest CVSS 8.9 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for in2code/powermail, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
12.5.2 M1 Yes Details →
12.5.1 M1 Yes Details →
12.5.0 M1 Yes Details →
12.4.4 M1 Yes Details →
12.4.3 M1 Yes Details →
12.4.2 M1 Yes Details →
12.4.1 M1 Yes Details →
12.4.0 M1 Yes Details →
12.3.5 M2 Yes Details →
12.3.4 M2 Yes Details →
12.3.3 M2 Yes Details →
12.3.2 M2 Yes Details →
12.3.1 M2 Yes Details →
12.3.0 M2 Yes Details →
12.2.1 M2 Yes Details →
12.2.0 M2 Yes Details →
12.1.1 M2 Yes Details →
12.1.0 M2 Yes Details →
12.0.3 M2 Yes Details →
12.0.2 M2 Yes Details →
12.0.1 M2 Yes Details →
12.0.0 M2 Yes Details →
11.2.0 M1 Yes Details →
11.1.0 M1 Yes Details →
11.0.1 M1 Yes Details →
11.0.0 M1 Yes Details →
7.5.0 M1 Yes Details →
7.4.4 M2 Yes Details →
7.4.3 M2 Yes Details →
7.4.2 M2 Yes Details →
7.4.1 M2 Yes Details →
7.4.0 M2 Yes Details →
7.3.1 M2 Yes Details →
7.3.0 M2 Yes Details →
7.2.0 M2 Yes Details →
7.1.0 M2 Yes Details →
7.0.0 M2 Yes Details →
6.2.0 M2 Yes Details →
6.1.0 M2 Yes Details →
6.0.0 M2 Yes Details →
5.6.0 M2 Yes Details →
5.5.0 M2 Yes Details →
5.4.0 M2 Yes Details →
5.3.2 M2 Yes Details →
5.3.1 M2 Yes Details →
5.3.0 M2 Yes Details →
5.2.2 M2 Yes Details →
5.2.1 M2 Yes Details →
5.2.0 M2 Yes Details →
5.1.0 M2 Yes Details →
5.0.1 M2 Yes Details →
5.0.0 M2 Yes Details →
4.4.0 M2 Yes Details →
4.3.5 M2 Yes Details →
4.3.4 M2 Yes Details →
4.3.3 M2 Yes Details →
4.3.2 M2 Yes Details →
4.3.1 M2 Yes Details →
4.3.0 M2 Yes Details →
4.2.0 M2 Yes Details →
4.1.0 M2 Yes Details →
4.0.2 M2 Yes Details →
4.0.1 M2 Yes Details →
4.0.0 M2 Yes Details →
3.22.1 M2 Yes Details →
3.22.0 M2 Yes Details →
3.21.1 M2 Yes Details →
3.21.0 M2 Yes Details →
3.20.0 M2 Yes Details →
3.19.0 M2 Yes Details →
3.18.2 M2 Yes Details →
3.18.1 M2 Yes Details →
3.18.0 M2 Yes Details →
3.17.0 M2 Yes Details →
3.16.0 M2 Yes Details →
3.15.0 M2 Yes Details →
3.14.0 M2 Yes Details →
3.13.0 M2 Yes Details →
3.12.0 M2 Yes Details →
3.11.2 M2 Yes Details →
3.11.1 M2 Yes Details →
3.11.0 M2 Yes Details →
3.10.1 M2 Yes Details →
3.10.0 M2 Yes Details →
3.9.0 M2 Yes Details →
3.8.0 M2 Yes Details →
3.7.0 M2 Yes Details →
3.6.0 M2 Yes Details →
3.5.0 M2 Yes Details →
3.4.0 M2 Yes Details →
3.3.0 M2 Yes Details →
3.2.0 M2 Yes Details →

Newest 92 of 92 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 5
  • 2024 3
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 9 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About in2code/powermail

Is in2code/powermail safe to use?

Vulert records 9 vulnerabilities for in2code/powermail in Packagist: 0 critical, 3 high, 5 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does in2code/powermail have?

9 vulnerabilities are recorded for in2code/powermail in the Packagist ecosystem: 0 critical, 3 high, 5 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new in2code/powermail vulnerabilities disclosed?

0 vulnerabilities were recorded for in2code/powermail in the last 12 months, and the oldest entry in this database dates to 02 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of in2code/powermail are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor in2code/powermail for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the in2code/powermail version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.