Skip to content
Fencer Vulns
medium 6.8

CVE-2004-0520 json

Cross-site scripting (XSS) vulnerability in mime.php for SquirrelMail before 1.4.3 allows remote attackers to insert arbitrary HTML and scr…

published 2004-06-03 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0519

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.1%
EPSS 7.1% chance of exploitation in 30 days, percentile 94%
public exploits
1
Exploit-DB

Summary

Cross-site scripting (XSS) vulnerability in mime.php for SquirrelMail before 1.4.3 allows remote attackers to insert arbitrary HTML and script via the content-type mail header, as demonstrated using read_body.php.

Patch / fix

  • squirrelmail RHEL 3 1.4.3-0.e3.1

red hat advisories RHSA-2004:240

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-2004-0520 updated

security flaw

  • Red Hat Desktop version 3 squirrelmail 1.4.3-0.e3.1 Red Hat Enterprise Linux AS version 3 squirrelmail 1.4.3-0.e3.1 Red Hat Enterprise Linux ES version 3 squirrelmail 1.4.3-0.e3.1 Red Hat Enterprise Linux WS version 3 squirrelmail 1.4.3-0.e3.1
    fixed: vendor fix RHSA-2004:240

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

Timeline

  1. First public exploit (EDB-24160)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-24160 SquirrelMail 1.x - Email Header HTML Injection remote, 2004-05-31
  • securityfocus.com http://www.securityfocus.com/bid/10439 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

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.