Show filters
41 Total Results
Displaying 21-30 of 41
Sort by:
Attacker Value
Unknown
CVE-2007-3636
Disclosure Date: July 10, 2007 (last updated October 04, 2023)
Multiple unspecified vulnerabilities in the G/PGP (GPG) Plugin 2.1 for Squirrelmail allow remote attackers to execute arbitrary commands via unspecified vectors. NOTE: this information is based upon a vague pre-advisory from a reliable researcher.
0
Attacker Value
Unknown
CVE-2007-3635
Disclosure Date: July 10, 2007 (last updated October 04, 2023)
Multiple unspecified vulnerabilities in the G/PGP (GPG) Plugin before 2.1 for Squirrelmail might allow "local authenticated users" to inject certain commands via unspecified vectors. NOTE: this might overlap CVE-2005-1924, CVE-2006-4169, or CVE-2007-3634.
0
Attacker Value
Unknown
CVE-2007-1262
Disclosure Date: May 11, 2007 (last updated October 04, 2023)
Multiple cross-site scripting (XSS) vulnerabilities in the HTML filter in SquirrelMail 1.4.0 through 1.4.9a allow remote attackers to inject arbitrary web script or HTML via the (1) data: URI in an HTML e-mail attachment or (2) various non-ASCII character sets that are not properly filtered when viewed with Microsoft Internet Explorer.
0
Attacker Value
Unknown
CVE-2007-2589
Disclosure Date: May 11, 2007 (last updated October 04, 2023)
Cross-site request forgery (CSRF) vulnerability in compose.php in SquirrelMail 1.4.0 through 1.4.9a allows remote attackers to send e-mails from arbitrary users via certain data in the SRC attribute of an IMG element.
0
Attacker Value
Unknown
CVE-2006-6142
Disclosure Date: December 05, 2006 (last updated October 04, 2023)
Multiple cross-site scripting (XSS) vulnerabilities in SquirrelMail 1.4.0 through 1.4.9 allow remote attackers to inject arbitrary web script or HTML via the (1) mailto parameter in (a) webmail.php, the (2) session and (3) delete_draft parameters in (b) compose.php, and (4) unspecified vectors involving "a shortcoming in the magicHTML filter."
0
Attacker Value
Unknown
CVE-2006-4019
Disclosure Date: August 11, 2006 (last updated October 04, 2023)
Dynamic variable evaluation vulnerability in compose.php in SquirrelMail 1.4.0 to 1.4.7 allows remote attackers to overwrite arbitrary program variables and read or write the attachments and preferences of other users.
0
Attacker Value
Unknown
CVE-2006-3665
Disclosure Date: July 18, 2006 (last updated October 04, 2023)
SquirrelMail 1.4.6 and earlier, with register_globals enabled, allows remote attackers to hijack cookies in src/redirect.php via unknown vectors. NOTE: while "cookie theft" is frequently associated with XSS, the vendor disclosure is too vague to be certain of this.
0
Attacker Value
Unknown
CVE-2006-2842
Disclosure Date: June 06, 2006 (last updated November 08, 2023)
PHP remote file inclusion vulnerability in functions/plugin.php in SquirrelMail 1.4.6 and earlier, if register_globals is enabled and magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary PHP code via a URL in the plugins array parameter. NOTE: this issue has been disputed by third parties, who state that Squirrelmail provides prominent warnings to the administrator when register_globals is enabled. Since the varieties of administrator negligence are uncountable, perhaps this type of issue should not be included in CVE. However, the original developer has posted a security advisory, so there might be relevant real-world environments under which this vulnerability is applicable
0
Attacker Value
Unknown
CVE-2006-0377
Disclosure Date: February 24, 2006 (last updated February 22, 2025)
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."
0
Attacker Value
Unknown
CVE-2006-0188
Disclosure Date: February 24, 2006 (last updated February 22, 2025)
webmail.php in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to inject arbitrary web pages into the right frame via a URL in the right_frame parameter. NOTE: this has been called a cross-site scripting (XSS) issue, but it is different than what is normally identified as XSS.
0