| Package | Affected versions | Patched versions |
|---|---|---|
| phpmailer/phpmailer | ≥ 6.1.8, < 6.4.1 | 6.4.1 |
| phpmailer | ≥ 6.1.8, ≤ 6.4.0 | |
| wordpress | ≥ 3.7, < 3.7.36≥ 3.8, < 3.8.36≥ 3.9, < 3.9.34≥ 4.0, < 4.0.33≥ 4.1, < 4.1.33≥ 4.2, < 4.2.30≥ 4.3, < 4.3.26≥ 4.4, < 4.4.25≥ 4.5, < 4.5.24≥ 4.6, < 4.6.21≥ 4.7, < 4.7.21≥ 4.8, < 4.8.17≥ 4.9, < 4.9.18≥ 5.0, < 5.0.13≥ 5.1, < 5.1.10≥ 5.2, < 5.2.11≥ 5.3, < 5.3.8≥ 5.4, < 5.4.6≥ 5.5, < 5.5.5≥ 5.6, < 5.6.4≥ 5.7, < 5.7.2 | 3.7.363.8.363.9.344.0.334.1.334.2.304.3.264.4.254.5.244.6.214.7.214.8.174.9.185.0.135.1.105.2.115.3.85.4.65.5.55.6.45.7.2 |
This is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8. An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP's support for .phar files. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See this article for more info.
This issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like any kind of URL are rejected.
Validate paths to loaded files using the same pattern as used in isPermittedPath() before using them in any PHP file function, such as file_exists. This method can't be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to all user-supplied paths passed into such functions; it's not a problem specific to PHPMailer.
This issue was found by Fariskhi Vidyan, reported and managed via Tidelift.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free