Loading vulnerability…
A cross-site scripting (XSS) vulnerability exists in Opera.dll in Opera browser versions prior to 9.61. The vulnerability is due to improper escaping of the anchor identifier (fragment) in URLs before storing them in the History Search database (md.dat). This allows an attacker to inject arbitrary web script or HTML that will be executed in the context of the user when the history is searched or displayed.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module: 'modules/exploits/multi/browser/opera_historysearch.rb'. The module exploits a cross-site scripting (XSS) vulnerability in Opera browser versions 9.50 to 9.61 (CVE-2008-4696). The exploit works by serving malicious HTML/JavaScript to a victim using a vulnerable Opera browser. The JavaScript abuses Opera's internal configuration URIs (such as 'opera:config' and 'opera:historysearch') to inject and execute arbitrary shell commands on the victim's Unix system. The payload is delivered via JavaScript, which manipulates Opera's mail handler settings to execute the attacker's command when a crafted 'mailto:' link is triggered. The module is operational and provides command execution capabilities, but is not weaponized for mass exploitation. The only file present is a Ruby script for Metasploit, which includes embedded JavaScript for the browser-based attack. No external network endpoints are hardcoded; the attack is delivered via the Metasploit HTTP server to the victim's browser.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.