SquirrelMail 1.4.22 (and other versions before 20170427_0200-SVN) allows post-authentication remote code execution via…
No fixed version listed yet.Check the vendor advisory. References ↓
SquirrelMail 1.4.22 and earlier versions before 20170427_0200-SVN contain a flaw in the initStream function of Deliver_SendMail.class.php, where escapeshellcmd() fails to escape whitespace in the -f$envelopefrom parameter of the sendmail command line. An authenticated user can exploit this by uploading a crafted sendmail.cf file as an email attachment and referencing it via the -C option in the Email Address personal setting, which causes sendmail to run arbitrary shell commands on the server when SquirrelMail is configured to use sendmail as a command-line program.
Official description · CVE.org
SquirrelMail 1.4.22 (and other versions before 20170427_0200-SVN) allows post-authentication remote code execution via a sendmail.cf file that is mishandled in a popen call. It's possible to exploit this vulnerability to execute arbitrary shell commands on the remote server. The problem is in the Deliver_SendMail.class.php with the initStream function that uses escapeshellcmd() to sanitize the sendmail command before executing it. The use of escapeshellcmd() is not correct in this case since it doesn't escape whitespaces, allowing the injection of arbitrary command parameters. The problem is in -f$envelopefrom within the sendmail command line. Hence, if the target server uses sendmail and SquirrelMail is configured to use it as a command-line program, it's possible to trick sendmail into using an attacker-provided configuration file that triggers the execution of an arbitrary command. For exploitation, the attacker must upload a sendmail.cf file as an email attachment, and inject the sendmail.cf filename with the -C option within the "Options > Personal Informations > Email Address" setting.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 9 years after disclosure. Public exploit code (Exploit-DB) appeared 3 days after disclosure.
- Disclosedday 0
- Public exploit codeExploit-DB+3 days
- First seen exploitedVulnCheck KEV evidence+9 yrs
What security researchers reported
Not named in any threat report yetAlso mentioned in 3 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Webworm: New burrowing techniques [WeLiveSecurity]31 Jul 2026
- New burrowing techniques24 May 2026
- New burrowing techniques20 May 2026