Skip to content
Fencer Vulns
medium 4.3

CVE-2006-0195 json

Interpretation conflict in the MagicHTML filter in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to conduct cross-site scripting (XSS…

published 2006-02-24 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0203

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

Interpretation conflict in the MagicHTML filter in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to conduct cross-site scripting (XSS) attacks via style sheet specifiers with invalid (1) "/*" and "*/" comments, or (2) a newline in a "url" specifier, which is processed by certain web browsers including Internet Explorer.

Patch / fix

  • squirrelmail RHEL 3 1.4.6-5.el3
  • squirrelmail RHEL 4 1.4.6-5.el4

red hat advisories RHSA-2006:0283

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2006-0195 updated

security flaw

  • Red Hat Desktop version 3 squirrelmail 1.4.6-5.el3 Red Hat Enterprise Linux AS version 3 squirrelmail 1.4.6-5.el3 Red Hat Enterprise Linux AS version 4 squirrelmail 1.4.6-5.el4 Red Hat Enterprise Linux Desktop version 4 squirrelmail 1.4.6-5.el4 Red Hat Enterprise Linux ES version 3 squirrelmail 1.4.6-5.el3 Red Hat Enterprise Linux ES version 4 squirrelmail 1.4.6-5.el4
    +2 more products
    Red Hat Enterprise Linux WS version 3 squirrelmail 1.4.6-5.el3 Red Hat Enterprise Linux WS version 4 squirrelmail 1.4.6-5.el4
    fixed: vendor fix RHSA-2006:0283

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.