FirefoxWeb browser · Mozilla

CVE-2006-2784

MEDIUM · 5.1 CVSS v2.0 Published 2006-06-02

Fix available

A fix is available. Upgrade to after 1.5.0.3 or later.

See remediation →

60/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The PLUGINSPAGE functionality in Mozilla Firefox before 1.5.0.4 allows remote user-assisted attackers to execute privileged code by tricking a user into installing missing plugins and selecting the "Manual Install" button, then using nested javascript: URLs. NOTE: the manual install button is used for downloading software from a remote web site, so this issue would not cross privilege boundaries if the user progresses to the point of installing malicious software from the attacker-controlled site.

Technical summary

dbcve analysis · moderate confidence

This is a client-side browser vulnerability in Mozilla Firefox versions prior to 1.5.0.4 involving the PLUGINSPAGE functionality. Attackers could execute privileged code by tricking users into selecting the 'Manual Install' button for missing plugins and exploiting nested javascript: URLs. The user's own action of installing software from an attacker-controlled site limits the actual privilege escalation in practice.

MitigationUpgrade to Firefox 1.5.0.4 or later to patch this vulnerability. For legacy systems that cannot upgrade, consider using browser sandboxing or isolation techniques.

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

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:<= 1.5.0.3

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

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

Am I affected?

dbcve checks

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

Check installed Firefox version

Open Firefox and navigate to Help > About, or check the application version via command line (e.g., firefox -v or locate the executable properties)

Affected if The version displayed is 1.5.0.3 or earlier (1.5.0, 1.0.x, or other versions prior to 1.5.0.4)
Confirm PLUGINSPAGE functionality is present

In the address bar, type about:config and search for 'plugin' - look for plugin.scan.plid.all and plugin.scan.Quickfind entries which control PLUGINSPAGE behavior

Affected if These preferences exist and are enabled (default in vulnerable versions)
Verify browser is not running in sandboxed mode

Check if Firefox is running with additional isolation such as sandboxing software, virtual machines, or restricted profiles that would prevent the Manual Install dialog from executing privileged code

Affected if The browser is running with default privileges and no additional isolation layers

You are affected if Firefox version is 1.5.0.3 or earlier and the user can interact with the Manual Install prompt for missing plugins without sandbox protection.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.5.0.3

Interim mitigation

Upgrade to Firefox 1.5.0.4 or later to patch this vulnerability. For legacy systems that cannot upgrade, consider using browser sandboxing or isolation techniques.

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-2006-2784 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2006-2784?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 1.5.0.3 or later

Severity 5.1 Medium

Exploit likelihood EPSS, next 30 days 1.8%

Affects: Firefox

Remediation

Need this fixed?

Fix this in Firefox 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2006-2784 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References