dbcve.org
Opera BrowserApplication · Opera

CVE-2012-3556

HIGH · 9.3 CVSS v2.0 Published 2012-06-14
Fix available
A fix is available. Upgrade to after 11.62 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Opera before 11.65 does not properly restrict the opening of a pop-up window in response to the first click of a double-click action, which makes it easier for user-assisted remote attackers to conduct cross-site scripting (XSS) attacks or execute arbitrary code via a crafted web site.

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

Opera before 11.65 contains a vulnerability where double-click actions improperly restrict pop-up window opening on the first click, allowing user-assisted remote attackers to inject malicious scripts (XSS) or execute arbitrary code via crafted websites.

MitigationUpgrade Opera to version 11.65 or later; since Opera is discontinued, migrate to a supported browser.

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
Opera BrowserApplication
Affected:<= 11.62= 5.0= 5.02= 5.10= 5.11= 5.12= 6.0= 6.1= 6.01= 6.02= 6.03= 6.04

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
Complete
Integrity
Complete
Availability
Complete

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

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 if Opera browser is installed
    Check for Opera installation: look in typical install locations such as C:\Program Files\Opera on Windows, /Applications/Opera on macOS, or /usr/bin/opera on Linux. Also check the system program files or use package management commands like dpkg -l | grep opera or rpm -qa | grep opera.
    Affected if Opera browser is found on the system
  2. Determine the installed Opera version
    Launch Opera and navigate to Help > About Opera, or check the version through the executable properties. On Windows, right-click the opera.exe file and view Properties > Details for version information.
    Affected if The displayed version is 11.62 or lower, or matches any of these specific versions: 5.0, 5.02, 5.10, 5.11, 5.12, 6.0, 6.1, 6.01, 6.02, 6.03, or 6.04
  3. Confirm the vulnerability is exploitable
    This vulnerability is inherent to how Opera handles double-click events for pop-up windows. No specific browser configuration toggle controls this behavior. The issue manifests when double-clicking on certain page elements that trigger pop-up window creation.
    Affected if The installed version is in the affected range and the user visits crafted malicious websites that exploit the double-click to pop-up window handling flaw

A user is affected if Opera browser version 11.62 or lower, or any of the specific older versions (5.x, 6.x series listed), is installed and running, since the vulnerability exists in those versions regardless of configuration settings.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 11.62
Interim mitigation

Upgrade Opera to version 11.65 or later; since Opera is discontinued, migrate to a supported browser.

Recommended fix High confidence

Opera 11.65 or later

  1. 1. Visit the official Opera website at www.opera.com to download the latest version
  2. 2. Locate and download Opera version 11.65 or later (the fixed release)
  3. 3. Close any running instances of the Opera browser
  4. 4. Run the installer and follow the prompts to complete the upgrade
  5. 5. After installation, verify the version by navigating to Menu > Help > About Opera to confirm version 11.65 or higher is installed
  6. 6. Test that browser functionality works normally after the upgrade
Caveat Opera 11.65 is a legacy version from 2012. Modern Opera (version 15+) uses a Chromium-based engine and has significant differences in features, extensions, and UI compared to Opera 11.x. Consider upgrading to the current Opera browser for better security and features, but test for compatibility with

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opera Browser 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-2012-3556 — 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-2012-3556 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