basicsecurity.net
Proof, not just disclosure.
Threats / Mozilla / CVE-2019-11707
CVE-2019-11707 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Mozilla Firefox and Thunderbird vulnerability

Mozilla Firefox and Thunderbird contain a type confusion vulnerability in Array.pop that allows remote code execution through malicious JavaScript, exploited in the wild.

Verdict

Today item — known-exploited.

A type confusion flaw in JavaScript object handling enables attackers to achieve code execution via crafted web content or email attachments. The vulnerability is actively exploited and carries high severity despite no CVSS score assignment.

CISA KEV Yes · 2022-05-233EPSS 0.37951 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 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 2022-05-23).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.37951 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Mozilla, Firefox and Thunderbird. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-843 · Type ConfusionMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious JavaScript that exploits type confusion in Array.pop to corrupt memory and bypass security checks.
Business
Users visiting compromised websites or opening malicious email attachments face arbitrary code execution on their systems.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I trigger the vulnerability through a web page or email message that the victim's browser or email client automatically processes.
Business
Attackers gain execution context within the browser or email application, potentially compromising user data and system integrity.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mozilla (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mozillaCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.