Show filters
12 Total Results
Displaying 1-10 of 12
Sort by:
Attacker Value
Unknown
CVE-2021-3603
Disclosure Date: June 17, 2021 (last updated February 22, 2025)
PHPMailer 6.4.1 and earlier contain a vulnerability that can result in untrusted code being called (if such code is injected into the host project's scope by other means). If the $patternselect parameter to validateAddress() is set to 'php' (the default, defined by PHPMailer::$validator), and the global namespace contains a function called php, it will be called in preference to the built-in validator of the same name. Mitigated in PHPMailer 6.5.0 by denying the use of simple strings as validator function names.
0
Attacker Value
Unknown
CVE-2021-34551
Disclosure Date: June 16, 2021 (last updated February 22, 2025)
PHPMailer before 6.5.0 on Windows allows remote code execution if lang_path is untrusted data and has a UNC pathname.
0
Attacker Value
Unknown
CVE-2020-36326
Disclosure Date: April 28, 2021 (last updated February 22, 2025)
PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.
0
Attacker Value
Unknown
CVE-2020-13625
Disclosure Date: June 08, 2020 (last updated February 21, 2025)
PHPMailer before 6.1.6 contains an output escaping bug when the name of a file attachment contains a double quote character. This can result in the file type being misinterpreted by the receiver or any mail relay processing the message.
0
Attacker Value
Unknown
CVE-2018-19296
Disclosure Date: November 16, 2018 (last updated November 08, 2023)
PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
0
Attacker Value
Unknown
CVE-2017-11503
Disclosure Date: July 20, 2017 (last updated November 26, 2024)
PHPMailer 5.2.23 has XSS in the "From Email Address" and "To Email Address" fields of code_generator.php.
0
Attacker Value
Unknown
CVE-2017-5223
Disclosure Date: January 16, 2017 (last updated November 25, 2024)
An issue was discovered in PHPMailer before 5.2.22. PHPMailer's msgHTML method applies transformations to an HTML document to make it usable as an email message body. One of the transformations is to convert relative image URLs into attachments using a script-provided base directory. If no base directory is provided, it resolves to /, meaning that relative image URLs get treated as absolute local file paths and added as attachments. To form a remote vulnerability, the msgHTML method must be called, passed an unfiltered, user-supplied HTML document, and must not set a base directory.
0
Attacker Value
Unknown
CVE-2016-10033
Disclosure Date: December 30, 2016 (last updated February 15, 2024)
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.
0
Attacker Value
Unknown
CVE-2016-10045
Disclosure Date: December 30, 2016 (last updated November 25, 2024)
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code by leveraging improper interaction between the escapeshellarg function and internal escaping performed in the mail function in PHP. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-10033.
0
Attacker Value
Unknown
CVE-2015-8476
Disclosure Date: December 16, 2015 (last updated October 05, 2023)
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.
0