Live › vulnerability › CVE-2016-10033
Go to dashboardPHPMailer's mail() code path fails to sanitize user-supplied input before passing it to a shell, so input can inject commands. An attacker who can reach the vulnerable mail form gets arbitrary code execution inside the application's context, and failed attempts crash it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| PHP PHPMailer | vendor | – | – |
| phpmailer project phpmailer | vendor | < 5.2.18 | 5.2.18 |
| wordpress | vendor | <= 4.7 | – |
| joomla joomla\! | vendor | >= 1.5.0, <= 3.6.5 | – |
Check the PHPMailer version in composer.lock or vendor/phpmailer/phpmailer and confirm it is 5.2.18 or newer; unknown whether the sources give a fixed version.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
This page as .md · .json · in your agent: get_signal("CVE-2016-10033")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.