CWE
79
Advisory Published
CVE Published
Updated

CVE-2011-2023: XSS

First published: Tue Jul 12 2011(Updated: )

An cross-site scripting (XSS) flaw was found in the way SquirrelMail performed sanitization of MIME messages containing certain &lt;style&gt; HTML tags. A remote attacker could provide a specially-crafted message, which once opened in SquirrelMail webmail client could lead to arbitrary JavaScript or HTML code execution. Upstream advisory: [1] <a href="http://www.squirrelmail.org/security/issue/2011-07-10">http://www.squirrelmail.org/security/issue/2011-07-10</a> Relevant patch: [2] <a href="http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail?view=revision&amp;revision=14121">http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail?view=revision&amp;revision=14121</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
SquirrelMail<=1.4.21
SquirrelMail=0.1
SquirrelMail=0.1.1
SquirrelMail=0.1.2
SquirrelMail=0.2
SquirrelMail=0.2.1
SquirrelMail=0.3
SquirrelMail=0.3.1
SquirrelMail=0.3pre1
SquirrelMail=0.3pre2
SquirrelMail=0.4
SquirrelMail=0.4pre1
SquirrelMail=0.4pre2
SquirrelMail=0.5
SquirrelMail=0.5pre1
SquirrelMail=0.5pre2
SquirrelMail=1.0
SquirrelMail=1.0.1
SquirrelMail=1.0.2
SquirrelMail=1.0.3
SquirrelMail=1.0.4
SquirrelMail=1.0.5
SquirrelMail=1.0.6
SquirrelMail=1.0pre1
SquirrelMail=1.0pre2
SquirrelMail=1.0pre3
SquirrelMail=1.1.0
SquirrelMail=1.1.1
SquirrelMail=1.1.2
SquirrelMail=1.1.3
SquirrelMail=1.2
SquirrelMail=1.2.0
SquirrelMail=1.2.0-rc3
SquirrelMail=1.2.1
SquirrelMail=1.2.2
SquirrelMail=1.2.3
SquirrelMail=1.2.4
SquirrelMail=1.2.5
SquirrelMail=1.2.6
SquirrelMail=1.2.6-rc1
SquirrelMail=1.2.7
SquirrelMail=1.2.8
SquirrelMail=1.2.9
SquirrelMail=1.2.10
SquirrelMail=1.2.11
SquirrelMail=1.3.0
SquirrelMail=1.3.1
SquirrelMail=1.3.2
SquirrelMail=1.4
SquirrelMail=1.4-rc1
SquirrelMail=1.4.0
SquirrelMail=1.4.0-rc1
SquirrelMail=1.4.0-rc2a
SquirrelMail=1.4.0-r1
SquirrelMail=1.4.1
SquirrelMail=1.4.2
SquirrelMail=1.4.2-r1
SquirrelMail=1.4.2-r2
SquirrelMail=1.4.2-r3
SquirrelMail=1.4.2-r4
SquirrelMail=1.4.2-r5
SquirrelMail=1.4.3
SquirrelMail=1.4.3-r3
SquirrelMail=1.4.3-rc1
SquirrelMail=1.4.3a
SquirrelMail=1.4.3aa
SquirrelMail=1.4.4
SquirrelMail=1.4.4-rc1
SquirrelMail=1.4.5
SquirrelMail=1.4.5-rc1
SquirrelMail=1.4.6
SquirrelMail=1.4.6-rc1
SquirrelMail=1.4.6_cvs
SquirrelMail=1.4.7
SquirrelMail=1.4.8
SquirrelMail=1.4.8.4fc6
SquirrelMail=1.4.9
SquirrelMail=1.4.9a
SquirrelMail=1.4.10
SquirrelMail=1.4.10a
SquirrelMail=1.4.11
SquirrelMail=1.4.12
SquirrelMail=1.4.13
SquirrelMail=1.4.15
SquirrelMail=1.4.15-rc1
SquirrelMail=1.4.15rc1
SquirrelMail=1.4.16
SquirrelMail=1.4.17
SquirrelMail=1.4.18
SquirrelMail=1.4.19
SquirrelMail=1.4.20

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2011-2023?

    CVE-2011-2023 has a moderate severity rating due to the potential for remote attackers to execute arbitrary JavaScript via crafted MIME messages.

  • How do I fix CVE-2011-2023?

    To fix CVE-2011-2023, upgrade SquirrelMail to version 1.4.21 or later, which addresses the vulnerability.

  • What versions of SquirrelMail are affected by CVE-2011-2023?

    CVE-2011-2023 affects all versions of SquirrelMail prior to 1.4.21, including several versions starting from 0.1 to 1.4.20.

  • Can CVE-2011-2023 lead to data theft?

    Yes, CVE-2011-2023 can potentially lead to data theft as an attacker may execute malicious scripts to access sensitive information.

  • Is there a workaround for CVE-2011-2023 if I cannot upgrade?

    A temporary workaround for CVE-2011-2023 is to disable MIME handling in SquirrelMail until an upgrade can be performed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203