Search for packages
Package details: pkg:composer/phpmailer/phpmailer@5.2.27
purl pkg:composer/phpmailer/phpmailer@5.2.27
Next non-vulnerable version 6.5.0
Latest non-vulnerable version 6.5.0
Risk 4.0
Vulnerabilities affecting this package (3)
Vulnerability Summary Fixed by
VCID-377c-stcv-abgs
Aliases:
CVE-2021-3603
GHSA-77mr-wc79-m8j3
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.
6.5.0
Affected by 0 other vulnerabilities.
VCID-vc72-ptj1-kyh4
Aliases:
CVE-2020-13625
GHSA-f7hx-fqxw-rvvj
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.
6.1.6
Affected by 2 other vulnerabilities.
VCID-x7mu-d5zc-zkbx
Aliases:
CVE-2021-34551
GHSA-7q44-r25x-wm4q
Remote Code Execution vulnerability in PHPMailer 6.4.1 running on Windows PHPMailer 6.4.1 contains a possible remote code execution vulnerability through the `$lang_path` parameter of the `setLanguage()` method. If the `$lang_path` parameter is passed unfiltered from user input, it can be set to [a UNC path](https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats#unc-paths), and if an attacker is also able to create a remote mount on the server that the UNC path points to, a script file under their control may be executed. ### Impact Arbitrary code may be run by a remote attacker under the web server or PHP process running on Window hosts. ### Patches Mitigated in PHPMailer 6.5.0 by no longer treating translation files as PHP code, but by parsing their text content directly. This approach avoids the possibility of executing unknown code while retaining backward compatibility. This isn't ideal, so the current translation format is deprecated and will be replaced in the next major release. ### Workarounds Any of: * Ensure that calling code does not pass unfiltered user-supplied data to the `$lang_path` parameter of the `setLanguage()` method. * Block or filter the use of unknown UNC paths in this parameter (or altogether). * Ensure that unauthorised users do not have the ability to read from unknown remote servers via UNC paths. * Run on an OS that does not support UNC paths ### References [CVE-2021-34551](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-34551). Reported by [listensec.com](https://listensec.com) via Tidelift. ### For more information If you have any questions or comments about this advisory: * Open an issue in [PHPMailer](https://github.com/PHPMailer/PHPMailer) * [Email the maintainers](mailto:phpmailer@synchromedia.co.uk)
6.5.0
Affected by 0 other vulnerabilities.
Vulnerabilities fixed by this package (1)
Vulnerability Summary Aliases
VCID-tgrc-1eek-q7e9 PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack. CVE-2018-19296
GHSA-7w4p-72j7-v7c2