dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-1125

MEDIUM · 5.8 CVSS v2.0 Published 2010-03-26
Fix available
A fix is available. Upgrade to after 2.0.4 or later.
See remediation →
67/100
Remediation priority · Elevated
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
The JavaScript implementation in Mozilla Firefox 3.x before 3.5.10 and 3.6.x before 3.6.4, and SeaMonkey before 2.0.5, allows remote attackers to send selected keystrokes to a form field in a hidden frame, instead of the intended form field in a visible frame, via certain calls to the focus method.

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

A JavaScript focus() method vulnerability in Firefox 3.x before 3.5.10 and 3.6.x before 3.6.4, and SeaMonkey before 2.0.5, allows remote attackers to redirect keystrokes intended for a form field in a visible frame to a hidden frame's form field instead, enabling keystroke theft through focus manipulation.

MitigationUpdate affected browsers to Firefox 3.5.10+, 3.6.4+, or SeaMonkey 2.0.5+; ensure automatic updates are enabled for browser software.

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:= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.7= 3.0.8= 3.0.9= 3.0.10= 3.0.11= 3.0.12
SeamonkeyApplication
Affected:<= 2.0.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
None

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

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. Identify installed Firefox version
    Open Firefox, click Help > About Firefox (or navigate to about:support). Note the version number displayed.
    Affected if Version is 3.0.x through 3.0.12, or 3.5.x before 3.5.10, or 3.6.x before 3.6.4
  2. Identify installed SeaMonkey version
    Open SeaMonkey, click Help > About SeaMonkey. Note the version number displayed.
    Affected if Version is 1.0.x, 1.1, or 2.0.x before 2.0.5
  3. Check if JavaScript is enabled
    In browser, go to Options/Preferences > Content (Firefox) or Edit > Preferences > Privacy & Security (SeaMonkey). Verify 'Enable JavaScript' checkbox is checked.
    Affected if JavaScript is enabled AND browser version falls into affected range listed above (the vulnerability requires JavaScript to execute the focus() manipulation)

User is affected if running Firefox 3.0.x, 3.5.x before 3.5.10, or 3.6.x before 3.6.4, OR SeaMonkey 1.0.x through 2.0.4, with JavaScript enabled.

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.4
Interim mitigation

Update affected browsers to Firefox 3.5.10+, 3.6.4+, or SeaMonkey 2.0.5+; ensure automatic updates are enabled for browser software.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-2010-1125 — 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-2010-1125 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