This weekExploitable · Confirmed
phpmailer/phpmailer: PHPMailer susceptible to arbitrary code execution
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
phpmailer/phpmailer (Packagist)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- phpmailer/phpmailer (Packagist): every version, before 5.2.10
The fix
phpmailer/phpmailer (Packagist) fixed in 5.2.10
composercomposer require "phpmailer/phpmailer:^5.2.10" --update-with-all-dependenciesCheck what is installedcomposer show phpmailer/phpmailerPaste into Cursor, Lovable or Claude CodeUpgrade the Packagist dependency phpmailer/phpmailer to 5.2.10 or the nearest later release, to fix CVE-2008-5619. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
EPSS puts the chance of exploitation in the next 30 days at 59%.
FIRST EPSSStated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)