[#13388] - Update to PHPMailer 5.2.21
- Fixed in Code Base
- 29 Dec 2016
- Medium
- Build: staging
- # 13388
- Diff
- mbabker:phpmailer-5.2.20
- Success continuous-integration/drone the build was successful Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Summary of Changes
Updates PHPMailer to 5.2.21. Composer is run with 1.3.0 which explains the ClassLoader and timestamp changes.
Testing Instructions
Mail sending works
Documentation Changes Required
N/A
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | External Library Libraries |
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13388.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13388.
| Milestone |
Added: |
||
| Labels |
Added:
?
?
|
||
| Title |
|
||||||
| Title |
|
||||||
I think this is important enough to justify a quick fix release...
No, it's not. See https://developer.joomla.org/security-centre/668-20161205-phpmailer-security-advisory.html and associated references.
I think this is important enough to justify a quick fix release...
See https://developer.joomla.org/security-centre/668-20161205-phpmailer-security-advisory.html
No action required for Joomla as the vulnerability isn't useable in core.
edit: Michael was faster
rdeutz
- | Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-12-29 10:36:50 |
| Closed_By | ⇒ | rdeutz | |
| Labels |
Added:
?
|
||
I have tested this item✅ successfully on 16e7dec
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13388.