PatchTheCVECVE-2018-19296: PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
56
This month
HIGH 8.8WATCHLISTUPGRADEMITIGATEMITIGATE
CVE-2018-19296 is a high-severity flaw (CVSS 8.8) affecting phpmailer, debian linux, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
Why this priority
- High severity
- On your watchlist
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
phpmailer project phpmailer UPGRADE
Affected: < 5.2.27 · >= 6.0.0 and < 6.0.6
Fixed in: 5.2.27, 6.0.6
Safe to downgrade to: a release before 6.0.0
1. Check installed version
apt-cache policy phpmailer || rpm -q phpmailer || phpmailer --version
2. UPGRADE to 5.2.27 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade phpmailer
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade phpmailer
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)
apt-cache madison phpmailer
sudo apt install phpmailer=<VERSION_BEFORE_6.0.0>
sudo apt-mark hold phpmailer
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list phpmailer
sudo dnf downgrade phpmailer-<VERSION_BEFORE_6.0.0>
sudo dnf versionlock add phpmailer
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
debian debian linux MITIGATE
Affected: 8.0 · 9.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
fedoraproject fedora MITIGATE
Affected: 33 · 34
Fixed in: no fixed release known
Safe to downgrade to: a release before 33
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
wordpress wordpress UPGRADE
Affected: >= 3.7 and <= 5.7
Fixed in: newer than 5.7
Safe to downgrade to: a release before 3.7
1. Check installed version
apt-cache policy wordpress || rpm -q wordpress || wordpress --version
2. UPGRADE to newer than 5.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade wordpress
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade wordpress
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.7 (Debian / Ubuntu)
apt-cache madison wordpress
sudo apt install wordpress=<VERSION_BEFORE_3.7>
sudo apt-mark hold wordpress
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list wordpress
sudo dnf downgrade wordpress-<VERSION_BEFORE_3.7>
sudo dnf versionlock add wordpress
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-19296?
phpmailer: upgrade to 5.2.27, 6.0.6; debian linux: mitigate or apply the listed mitigation; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-19296 being exploited?
CVE-2018-19296 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-19296 affect?
CVE-2018-19296 affects phpmailer, debian linux, fedora. Severity is high (CVSS 8.8). PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
How urgent is CVE-2018-19296?
Priority 56/100. High severity; On your watchlist
Software pages
WordPress vulnerabilities · Debian vulnerabilities
Related CVEs
- CVE-2021-3603 HIGH 8.1 UPGRADE MITIGATE PHPMailer 6.4.1 and earlier contain a vulnerability that can result in untrusted code being called (if such co
- CVE-2021-34551 HIGH 8.1 UPGRADE MITIGATE PHPMailer before 6.5.0 on Windows allows remote code execution if lang_path is untrusted data and has a UNC pa
- CVE-2020-36326 CRITICAL 9.8 UPGRADE UPGRADE PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UN
- CVE-2020-13625 HIGH 7.5 UPGRADE MITIGATE PHPMailer before 6.1.6 contains an output escaping bug when the name of a file attachment contains a double qu
- CVE-2017-5223 MEDIUM 5.5 UPGRADE An issue was discovered in PHPMailer before 5.2.22