CVE-2012-6460
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 · uneditedOpera before 11.67 and 12.x before 12.02 allows remote attackers to cause truncation of a dialog, and possibly trigger downloading and execution of arbitrary programs, 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 · moderate confidenceOpera browsers before versions 11.67 and 12.02 contain a vulnerability where visiting a crafted website can cause dialog truncation. This dialog manipulation can potentially be exploited to trigger downloading and execution of arbitrary programs on the affected system.
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<= 11.66= 1.00= 2.00= 2.10= 2.12= 3.00= 3.10= 3.21= 3.50= 3.51= 3.60= 3.61CVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Opera browser installationSearch for Opera executable (opera.exe) in common installation directories such as C:\Program Files\Opera, C:\Program Files (x86)\Opera, or check registry under HKEY_LOCAL_MACHINE\SOFTWARE\Opera Software or HKEY_CURRENT_USER\Software\Opera SoftwareAffected if Opera browser is found installed on the system
-
Determine installed Opera versionRight-click opera.exe, select Properties, then view the Details tab for version information. Alternatively, launch Opera, go to Help > About Opera to view the exact version numberAffected if The displayed version is 11.66 or earlier, or falls within the listed affected version numbers (11.00, 2.00, 2.10, 2.12, 3.00, 3.10, 3.21, 3.50, 3.51, 3.60, 3.61)
-
Identify Opera product typeCheck the Help > About Opera dialog to confirm the specific Opera product name and build number, as some listed versions may refer to different Opera-based products or bundled versionsAffected if The product is a version of Opera Browser at 11.66 or lower, or matches any version explicitly listed in the affected products range
The system is affected if any Opera browser installation found is version 11.66 or earlier, or matches the specific affected version numbers, and the browser is capable of rendering web content and displaying dialogs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Opera to version 11.67 or 12.02 and later, or migrate to a supported browser. Organizations should identify and remediate any remaining installations of vulnerable Opera versions.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-6460 in production — separate from our analysis above.
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.
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.
- 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