No. CVE-2016-10033
A PHPMailer bug is being used in attacks
Yes. Attackers are using this right now.
What to do
Apply the vendor's update. If there is none, stop using it or cut it off from the internet.
- Confirmed in attacks
- Jul 7, 2025
- Product
- PHPMailer
- Attack likelihood, next 30 days
- over 99%
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official description
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.
For your tech helper
A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is PHP PHPMailer (CVE-2016-10033) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2016-10033. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.