CVE-2009-1581

CVE-2009-1581 is a medium-severity vulnerability in Squirrelmail with a CVSS 2.0 base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-79.

Key facts

Description

functions/mime.php in SquirrelMail before 1.4.18 does not protect the application's content from Cascading Style Sheets (CSS) positioning in HTML e-mail messages, which allows remote attackers to spoof the user interface, and conduct cross-site scripting (XSS) and phishing attacks, via a crafted message.

Frequently asked questions

What is CVE-2009-1581?
functions/mime.php in SquirrelMail before 1.4.18 does not protect the application's content from Cascading Style Sheets (CSS) positioning in HTML e-mail messages, which allows remote attackers to spoof the user interface, and conduct cross-site scripting (XSS) and phishing attacks, via a crafted message.
How severe is CVE-2009-1581?
CVE-2009-1581 has a CVSS 2.0 base score of 4.3, rated medium severity.
Is CVE-2009-1581 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-1581?
CVE-2009-1581 primarily affects Squirrelmail. In total, 59 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-1581?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2009-1581 published?
CVE-2009-1581 was published on 2009-05-14 and last updated on 2026-06-16.

References

Affected products (59)

More vulnerabilities in Squirrelmail

All CVEs affecting Squirrelmail →

Other CWE-79 (Cross-site Scripting (XSS)) vulnerabilities

Browse all CWE-79 (Cross-site Scripting (XSS)) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: