Phpmailer

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.

Published: 2021-06-17T12:09:42.000Z
Updated: 2024-08-03T17:01:07.074Z

PHPMailer before 6.5.0 on Windows allows remote code execution if lang_path is untrusted data and has a UNC pathname.

Published: 2021-06-16T17:23:18.000Z
Updated: 2024-08-04T00:12:50.377Z

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.

Published: 2021-04-28T02:21:53.000Z
Updated: 2024-08-04T17:23:10.518Z

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.

Published: 2020-06-08T16:03:22.000Z
Updated: 2024-08-04T12:25:16.318Z

PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.

Published: 2018-11-16T09:00:00.000Z
Updated: 2024-08-05T11:30:04.081Z