Skip to content
Fencer Intel
medium 5.0

CVE-2015-8476 json

SMTP Injection in PHPMailer

published 2015-12-16 10 y ago modified 2026-06-17 4 mo ago also GHSA-738m-f33v-qc2r , EUVD-2020-0337

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

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 or (2) SMTP command to the sendCommand function in class.smtp.php, a different vulnerability than CVE-2012-0796.

Patch / fix

  • packagist phpmailer/phpmailer 5.2.14
  • libphp-phpmailer Debian 14, Debian 13, Debian 12 5.2.14+dfsg-1

debian advisories DEBIAN-CVE-2015-8476

  • libphp-phpmailer Ubuntu 14.04 LTS 5.1-1+deb6u11build0.14.04.1

ubuntu advisories UBUNTU-CVE-2015-8476

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-8476 updated cvss 4.3

php-PHPMailer: Message injection caused by line breaks in addresses

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
packagist phpmailer/phpmailer
>=5.0.0, <5.2.14
5.2.14

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.