Login Request a demo
Unscored severity · published Feb 24, 2006
CVE-2006-0377
CRLF injection vulnerability in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to inject arbitrary IMAP commands via newline characters in the mailbox parameter of the…
–
CVSS
2.4%
EPSS
No
On KEV
Description
CRLF injection vulnerability in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to inject arbitrary IMAP commands via newline characters in the mailbox parameter of the sqimap_mailbox_select command, aka "IMAP injection."
Exploitation
Is it being used?
Exploit prediction (EPSS)2.4% · higher than 84% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SQ
Squirrelmail · Squirrelmail
1.4; 1.4.1; 1.4.2; 1.4.3; 1.4.3_r3; 1.4.3_rc1; +6 more · source: NVD
Affected product
SQ
Squirrelmail
Squirrelmail
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2006-0377
CVE.org
https://www.cve.org/CVERecord?id=CVE-2006-0377
Vendor Advisory
http://secunia.com/advisories/18985
secunia.com
http://secunia.com/advisories/19130
secunia.com
http://secunia.com/advisories/19131
secunia.com
http://secunia.com/advisories/19176
secunia.com
http://secunia.com/advisories/19205
More from Squirrelmail
9.8
CVE-2020-14932
compose.php in SquirrelMail 1.4.22 calls unserialize for the $mailtodata value, which originates from an HTTP GET request
8.8
CVE-2020-14933
compose.php in SquirrelMail 1.4.22 calls unserialize for the $attachments value, which originates from an HTTP POST request
8.8
CVE-2018-8741
A directory traversal flaw in SquirrelMail 1.4.22 allows an authenticated attacker to exfiltrate (or potentially delete) files from the hosting server, related to ../ in the…
8.8
CVE-2017-7692
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
7.2
CVE-2025-30090
mime.php in SquirrelMail through 1.4.23-svn-20250401 and 1.5.x through 1.5.2-svn-20250401 allows XSS via e-mail headers, because JavaScript payloads are mishandled after $encoded…