Skip to content

build(deps): bump phpmailer/phpmailer from 6.4.0 to 6.5.3

Created by: dependabot[bot]

Bumps phpmailer/phpmailer from 6.4.0 to 6.5.3.

Release notes

Sourced from phpmailer/phpmailer's releases.

PHPMailer 6.5.3

This is a maintenance release.

  • Wrong commit tagged for the 6.5.2 release!
  • Version file updated

PHPMailer 6.5.2

This is a maintenance release.

  • Enable official support for PHP 8.1
  • Enable experimental support for PHP 8.2
  • Fix for PHP 5.6
  • Fix for incorrect options for punyencoding IDNs

PHPMailer 6.5.1

This is a maintenance release.

  • Provisional support for PHP 8.1
  • Major overhaul of test suite
  • Add codecov.io coverage reporting
  • Prefer implicit TLS on port 465 as default encryption scheme in examples, as per RFC8314
  • Fix potential noisy output from IMAP address parser
  • Stricter checking of custom MessageID validity
  • Replace invalid default From address
  • Support fallback for languages, so a request for pt_xx will fall back to pt rather than the default en.
  • Support multi-line RFC2047-encoded addresses in parseAddresses
  • Improved Japanese translation

Many thanks to @​jrfnl for all her work.

PHPMailer 6.5.0

This is a security release.

  • SECURITY Fixes CVE-2021-34551, a complex RCE affecting Windows hosts. See https://github.com/PHPMailer/PHPMailer/blob/HEAD/SECURITY.md for details.
  • The fix for this issue changes the way that language files are loaded. While they remain in the same PHP-like format, they are processed as plain text, and any code in them will not be run, including operations such as concatenation using the . operator.
  • Deprecation The current translation file format using PHP arrays is now deprecated; the next major version will introduce a new format.
  • SECURITY Fixes CVE-2021-3603 that may permit untrusted code to be run from an address validator. See https://github.com/PHPMailer/PHPMailer/blob/HEAD/SECURITY.md for details.
  • The fix for this issue includes a minor BC break: callables injected into validateAddress, or indirectly through the $validator class property, may no longer be simple strings. If you want to inject your own validator, provide a closure instead of a function name.
  • Haraka message ID strings are now recognised

Thanks to Vikrant Singh Chauhan, listensec.com, and the WordPress security team for reporting and assistance with this release.

PHPMailer 6.4.1

This is a security release.

  • SECURITY Fixes CVE-2020-36326, a regression of CVE-2018-19296 object injection introduced in 6.1.8, see SECURITY.md for details
  • Reject more file paths that look like URLs, matching RFC3986 spec, blocking URLS using schemes such as ssh2
  • Ensure method signature consistency in doCallback calls
  • Ukrainian language update
  • Add composer scripts for checking coding standards and running tests

... (truncated)

Changelog

Sourced from phpmailer/phpmailer's changelog.

Version 6.5.3 (November 25th, 2021)

  • Wrong commit tagged for the 6.5.2 release!
  • Version file updated

Version 6.5.2 (November 25th, 2021)

  • Enable official support for PHP 8.1
  • Enable experimental support for PHP 8.2
  • Fix for PHP 5.6
  • Fix for incorrect options for punyencoding IDNs

Version 6.5.1 (August 18th, 2021)

  • Provisional support for PHP 8.1
  • Major overhaul of test suite
  • Add codecov.io coverage reporting
  • Prefer implicit TLS on port 465 as default encryption scheme in examples, as per RFC8314
  • Fix potential noisy output from IMAP address parser
  • Stricter checking of custom MessageID validity
  • Replace invalid default From address
  • Support fallback for languages, so a request for pt_xx will fall back to pt rather than the default en.
  • Support multi-line RFC2047 addresses in parseAddresses
  • Improved Japanese translation

Many thanks to @​jrfnl for all her work.

Version 6.5.0 (June 16th, 2021)

  • SECURITY Fixes CVE-2021-34551, a complex RCE affecting Windows hosts. See https://github.com/PHPMailer/PHPMailer/blob/master/SECURITY.md for details.
  • The fix for this issue changes the way that language files are loaded. While they remain in the same PHP-like format, they are processed as plain text, and any code in them will not be run, including operations such as concatenation using the . operator.
  • Deprecation The current translation file format using PHP arrays is now deprecated; the next major version will introduce a new format.
  • SECURITY Fixes CVE-2021-3603 that may permit untrusted code to be run from an address validator. See https://github.com/PHPMailer/PHPMailer/blob/master/SECURITY.md for details.
  • The fix for this issue includes a minor BC break: callables injected into validateAddress, or indirectly through the $validator class property, may no longer be simple strings. If you want to inject your own validator, provide a closure instead of a function name.
  • Haraka message ID strings are now recognised

Version 6.4.1 (April 29th, 2021)

  • SECURITY Fixes CVE-2020-36326, a regression of CVE-2018-19296 object injection introduced in 6.1.8, see SECURITY.md for details
  • Reject more file paths that look like URLs, matching RFC3986 spec, blocking URLS using schemes such as ssh2
  • Ensure method signature consistency in doCallback calls
  • Ukrainian language update
  • Add composer scripts for checking coding standards and running tests
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Merge request reports