CVE-2012-1928
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.62 allows remote attackers to spoof the address field by triggering a page reload followed by a redirect to a different domain.
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 confidenceOpera before 11.62 contains an address bar spoofing vulnerability where a remote attacker can manipulate the browser to display one domain in the address field while rendering content from a different domain. This is achieved by triggering a page reload followed by a redirect, causing the address bar to remain anchored to the original domain.
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.61= 5.0= 5.02= 5.10= 5.11= 5.12= 6.0= 6.1= 6.01= 6.02= 6.03= 6.04CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:P/A:P
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.
-
Check installed Opera versionOpen Opera and navigate to Help > About Opera, or run 'opera --version' from command line. On Windows, the version may also be visible in Add/Remove Programs.Affected if The displayed version is 11.61 or lower, or matches any of these: 5.0, 5.02, 5.10, 5.11, 5.12, 6.0, 6.1, 6.01, 6.02, 6.03, 6.04
-
Confirm browser engine typeCheck if the installed Opera is the legacy Presto-based engine (versions 12 and earlier) or the newer Chromium-based Opera (version 15 and later). This can be determined from the version number and About dialog.Affected if The browser is Opera versions 12 or earlier using the Presto rendering engine, as the Chromium-based variants are not affected by this specific flaw.
-
Identify if address bar manipulation is possibleAttempt to reproduce the vulnerability by loading a page, triggering a reload (F5 or Ctrl+R), and immediately following with a JavaScript redirect (window.location) before the reload completes. Observe whether the address bar displays the original domain while content loads from a different origin.Affected if The address bar shows the original domain while content from a different domain renders, confirming the spoofing vulnerability is present.
The environment is affected if Opera with Presto engine version 11.61 or earlier (including the listed older versions) is installed and the address bar can be made to display one domain while rendering content from a different domain.
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.62 or later. If using a maintained Chromium-based Opera variant, ensure it receives current security updates. For web applications, implement Content Security Policy headers to mitigate phishing risks from address spoofing.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1928 — 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-1928 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