Actively exploited vulnerability
PHPMailer: code execution flaw under attack
CVE-2016-10033 · PHPMailer Command Injection Vulnerability
What is affected
PHPMailer is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.
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.
What an attacker can do
This is a code execution flaw. It lets an attacker run their own commands or programs on the affected system. In practice that usually means taking it over: installing malware, stealing data or using it to reach other devices on the same network.
- How it is reached
- Over the internet or network
- Access the attacker needs
- No account needed
- Does the victim have to do something?
- No, works without the victim doing anything
What to do
- At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
- If you administer PHPMailer at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
- If the product is past its support date and no fix exists, take it off the internet or retire it.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor advisories and fixes
- github.comgithub.com/PHPMailer/PHPMailer/releases/tag/v5.2.18
- github.comgithub.com/advisories/GHSA-5f37-gxvh-23v6
How urgent is it
CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on July 7, 2025, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by July 28, 2025, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.
The EPSS model estimates a 100% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 100.0% of all scored vulnerabilities.
Its CVSS severity score is 9.8 out of 10 (critical), as recorded in the US National Vulnerability Database.
Technical description
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 quote) in a crafted Sender property.