dbcve.org
Opera BrowserApplication · Opera

CVE-2007-1737

HIGH · 7.5 CVSS v2.0 Published 2007-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 9.10 does not check URLs embedded in (1) object or (2) iframe HTML tags against the phishing site blacklist, which allows remote attackers to bypass phishing protection.

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 9.10's built-in phishing blacklist protection does not get applied to URLs loaded within object or iframe HTML tags, allowing attackers to host malicious content in these elements while evading Opera's anti-phishing filter.

MitigationUpgrade to a later version of Opera that properly checks all embedded URLs against the phishing blacklist, or use an alternative browser with current security updates.

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:= 9.10

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/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 checks

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

  1. Verify Opera Browser is installed
    Check for Opera executable in common installation paths (e.g., C:\Program Files\Opera\opera.exe on Windows, /Applications/Opera.app on macOS, or via command: which opera or dpkg -l | grep opera on Linux)
    Affected if Opera Browser is not found on the system
  2. Confirm installed Opera version
    Run Opera with --version flag or check the version in Opera's About dialog (Help > About Opera). Compare the exact version number to the affected range.
    Affected if The installed version is exactly 9.10
  3. Check if phishing filter is enabled
    In Opera 9.10, go to Tools > Preferences > Security > Enable fraud and malware protection, or inspect Opera's configuration files (operapref.ini or opera6.ini) for the FraudCheckEnabled setting
    Affected if The phishing filter is enabled and the Opera version is 9.10 (the bypass only matters when the feature is active)

You are affected if Opera Browser version 9.10 is installed with the fraud/malware protection feature enabled, as the phishing blacklist will not be applied to URLs loaded within object or iframe HTML tags.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a later version of Opera that properly checks all embedded URLs against the phishing blacklist, or use an alternative browser with current security updates.

Fix this in Opera Browser Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get help mitigating

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-2007-1737 — 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-2007-1737 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