Phpmailer Project vulnerabilities1 known to be exploited.
Phpmailer Project has 10 published vulnerabilities across 1 product in our catalogue. 1 of them is on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Phpmailer, with 10. If you run Phpmailer Project software, patch the exploited flaws first.
The most recent Phpmailer Project flaw added to the known-exploited list is CVE-2016-10033, on 7 July 2025. We keep watching the known-exploited list.
Which Phpmailer Project products have the most vulnerabilities?
Phpmailer leads with 10 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Phpmailer Project vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8PHPMailer Command Injection Vulnerability
PHPMailer contains a command injection vulnerability because it fails to sanitize user-supplied input.
Which Phpmailer Project flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \" (backslash double...
- 98%CVE-2016-10045Critical
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code by leveraging improper interaction between the...
- 3.8%CVE-2020-13625High
PHPMailer before 6.1.6 contains an output escaping bug when the name of a file attachment contains a double quote character.
- 3.1%CVE-2020-36326Critical
PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname.
- 2.8%CVE-2021-34551High
PHPMailer before 6.5.0 on Windows allows remote code execution if lang_path is untrusted data and has a UNC pathname.
- 2.4%CVE-2017-11503Medium
PHPMailer 5.2.23 has XSS in the "From Email Address" and "To Email Address" fields of code_generator.php.
- 2.3%CVE-2021-3603High
PHPMailer 6.4.1 and earlier contain a vulnerability that can result in untrusted code being called (if such code is injected into the host project's scope by other means).
- 2.2%CVE-2018-19296High
PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
- 2.1%CVE-2017-5223Medium
An issue was discovered in PHPMailer before 5.2.22.
- 2.0%CVE-2015-8476Medium
Multiple CRLF injection vulnerabilities in PHPMailer before 5.2.14 allow attackers to inject arbitrary SMTP commands via CRLF sequences in an (1) email address to the validateAddress function in class.phpmailer.php...
All Phpmailer Project products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Phpmailer Project? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
PHPMailer contains a command injection vulnerability because it fails to sanitize user-supplied input. Specifically, this issue affects the 'mail()' function of 'class.phpmailer.php' script. An attacker can exploit this issue to execute arbitrary code within the context of the application. Failed exploit attempts will result in a denial-of-service condition.
- Matched to
- Phpmailer on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 10 published vulnerabilities across 1 product and 51 versions from Phpmailer Project. The most recent Phpmailer Project flaw added to the known-exploited list is CVE-2016-10033, on 7 July 2025.
1 Phpmailer Project vulnerability is on the list of flaws known to be exploited. The most recently added is CVE-2016-10033. The full list is on this page.
Phpmailer, with 10 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Phpmailer Project products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.