phlymail vulnerabilities and fixes
Recent CVEs affecting phlymail, with upgrade or downgrade steps. 3 tracked.
phlymail has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-12-31. Highest priority: CVE-2005-2606 (score 44/100).
- CVE-2005-4666 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in PHlyMail before 3.3 Beta1 allows remote attackers to inject arbitr
- CVE-2005-4652 MEDIUM 6.4 DOWNGRADE SQL injection vulnerability in PHlyMail 3.02.01 allows remote attackers to execute arbitrary SQL commands via
- CVE-2005-2606 HIGH 7.5 DOWNGRADE Unknown vulnerability in the "frontend authentication" in PHlyMail 3.02.00 has unknown impact and attack vecto
FAQ
How do I fix phlymail vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is phlymail being exploited right now?
None of the tracked phlymail CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which phlymail CVE should I patch first?
CVE-2005-2606 currently ranks highest (44/100): Unknown vulnerability in the "frontend authentication" in PHlyMail 3.02.00 has unknown impact and attack vecto.