Skip to content
Fencer Vulns
medium 5.0

CVE-2006-0296 json

The XULDocument.persist function in Mozilla, Firefox before 1.5.0.1, and SeaMonkey before 1.0 does not validate the attribute name, which a…

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

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

Summary

The XULDocument.persist function in Mozilla, Firefox before 1.5.0.1, and SeaMonkey before 1.0 does not validate the attribute name, which allows remote attackers to execute arbitrary Javascript by injecting RDF data into the user's localstore.rdf file.

Patch / fix

  • thunderbird Debian 14, Debian 13, Debian 12 1.5.0.2-1

debian advisories DEBIAN-CVE-2006-0296

  • thunderbird RHEL 4 1.0.8-1.4.1
  • firefox RHEL 4 1.0.7-1.4.3

red hat advisories RHSA-2006:0330RHSA-2006:0200

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-0296 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 firefox 1.0.7-1.4.3, thunderbird 1.0.8-1.4.1 Red Hat Enterprise Linux Desktop version 4 firefox 1.0.7-1.4.3, thunderbird 1.0.8-1.4.1 Red Hat Enterprise Linux ES version 4 firefox 1.0.7-1.4.3, thunderbird 1.0.8-1.4.1 Red Hat Enterprise Linux WS version 4 firefox 1.0.7-1.4.3, thunderbird 1.0.8-1.4.1
    fixed: vendor fix RHSA-2006:0200

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

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

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/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.