CVE-2021-3603: Inclusion of Functionality from Untrusted Control Sphere in PHPMailer/PHPMailer

Published Jun 16, 2021
·
Updated

If a function is defined that has the same name as the default built-in email address validation scheme (php), it will be called in default configuration as when no validation scheme is provided, the default scheme's callable php was being called. If an attacker is able to inject such a function into the application (a much bigger issue), it will be called whenever an email address is validated, such as when calling validateAddress().

Impact Low impact – exploitation requires that an attacker can already inject code into an application, but it provides a trigger pathway.

Patches This is patched in PHPMailer 6.5.0 by denying the use of simple strings as validator function names, which is a very minor BC break.

Workarounds Inject your own email validator function.

References Reported by Vikrant Singh Chauhan via huntr.dev. CVE-2021-3603

For more information If you have any questions or comments about this advisory: Open an issue in the PHPMailer project Email us.

Other sources

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.

Launchpad

Untrusted code may be run from an overridden address validator

Affected Software

6 affected componentsFixes available
composer/phpmailer/phpmailer<6.5.0
6.5.0
composer/phpmailer/phpmailer<6.5.0
6.5.0
debian/libphp-phpmailer<=6.2.0-2
6.6.3-16.9.1-1
PHPMailer project PHPMailer<=6.4.1
Fedoraproject Fedora=33
Fedoraproject Fedora=34

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/phpmailer/phpmailer to a version that resolves this vulnerability.

    Fixed in 6.5.0
  2. Upgrade

    Upgrade debian/libphp-phpmailer to a version that resolves this vulnerability.

    Fixed in 6.6.3-1Fixed in 6.9.1-1
  3. Upgrade

    Upgrade PHPMailer/PHPMailer to a version that resolves this vulnerability.

    Fixed in 6.5.0
  4. Configuration

    Do not set PHPMailer::$validator / validateAddress() $patternselect to a simple string (e.g., 'php'); PHPMailer 6.5.0 mitigates by denying simple string validator function names.

    PHPMailer validateAddress() $patternselect = 'php' denied as simple string validator function name

Event History

Jun 16, 2021
Advisory Published
04:20 PM
Jun 17, 2021
CVE Published
via MITRE·12:09 PM
Data Sourced
via MITRE·12:09 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:57 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·02:33 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is CVE-2021-3603?

CVE-2021-3603 is a vulnerability that allows untrusted code to be run from an overridden address validator.

2

What software is affected by CVE-2021-3603?

The software affected by CVE-2021-3603 is phpmailer version up to and excluding 6.5.0.

3

How do I fix CVE-2021-3603?

To fix CVE-2021-3603, update phpmailer to version 6.5.0 or higher.

4

Where can I find more information about CVE-2021-3603?

More information about CVE-2021-3603 can be found at the following link: https://github.com/PHPMailer/PHPMailer/releases/tag/v6.5.0

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203