dbcve.org
FirefoxWeb browser · Mozilla

CVE-2007-1095

MEDIUM · 6.8 CVSS v2.0 Published 2007-02-26
Fix available
A fix is available. Upgrade to after 2.0.0.7 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Mozilla Firefox before 2.0.0.8 and SeaMonkey before 1.1.5 do not properly implement JavaScript onUnload handlers, which allows remote attackers to run certain JavaScript code and access the location DOM hierarchy in the context of the next web site that is visited by a client.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a browser-side vulnerability in older versions of Firefox (before 2.0.0.8) and SeaMonkey (before 1.1.5) where onUnload event handlers are not properly isolated. When a user navigates from a malicious page to a legitimate site, the attacker can execute JavaScript in the context of the new site and access the location DOM hierarchy, enabling cross-site scripting or session hijacking.

MitigationUpgrade affected browsers to Firefox 2.0.0.8+, SeaMonkey 1.1.5+, or migrate to supported browser versions. This is a client-side vulnerability with no server-side remediation possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FirefoxWeb browser
Affected:<= 2.0.0.7= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9
SeamonkeyApplication
Affected:<= 1.1.4= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Firefox browser version
    Open Firefox and navigate to Help > About Firefox (or press Alt+H then A on Windows; on macOS go to Firefox > About Firefox). Note the version number displayed.
    Affected if The displayed version is 2.0.0.7 or earlier, or falls within 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, or 0.9.
  2. Check SeaMonkey browser version
    Open SeaMonkey and navigate to Help > About SeaMonkey. Note the version number displayed.
    Affected if The displayed version is 1.1.4 or earlier, or falls within 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, or 1.1.
  3. Verify browser application in use
    Identify which browser application is currently in use. This vulnerability only affects Firefox and SeaMonkey; other browsers (Chrome, Internet Explorer, Opera) are not impacted by this specific CVE.
    Affected if The user is actively running an affected version of Firefox or SeaMonkey as identified in steps 1 or 2.

A user is affected if they are running any version of Firefox <= 2.0.0.7 (or the specific early versions listed) or any version of SeaMonkey <= 1.1.4 (or the specific versions 1.0 through 1.1).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.0.0.7
Interim mitigation

Upgrade affected browsers to Firefox 2.0.0.8+, SeaMonkey 1.1.5+, or migrate to supported browser versions. This is a client-side vulnerability with no server-side remediation possible.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1095 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data