Threats / Mozilla / CVE-2010-3765
CVE-2010-3765
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Mozilla Multiple Products vulnerability
Mozilla Firefox, SeaMonkey, and Thunderbird contain a memory corruption vulnerability in JavaScript frame construction that allows remote code execution when JavaScript is enabled.
Verdict
Today item — known-exploited.
Remote attackers can execute arbitrary code by exploiting incorrect index tracking in nsCSSFrameConstructor::ContentAppended during DOM manipulation, triggering memory corruption through multiple frame creation.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-06).
Probability (EPSS)
EPSS 0.83279 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Mozilla, Multiple Products. Confirm exact fixed builds in the vendor advisory.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious webpage containing JavaScript that manipulates the DOM via appendChild to trigger incorrect frame indexing.
Business
Users visiting the attacker's site with JavaScript enabled face arbitrary code execution on their systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the memory corruption to gain code execution within the browser process with user privileges.
Business
Attackers gain ability to steal credentials, install malware, or pivot to other systems on the user's network.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05