Worldweaver DX Studio Player versions prior to 3.0.29.1, when used as a Firefox plug-in, expose the shell.execute JavaScript API method without proper access restrictions. This allows remote attackers to craft malicious .dxstudio files that invoke shell.execute, resulting in arbitrary command execution on the victim's system.
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 (1 hidden).
This repository contains a single Metasploit exploit module targeting a command execution vulnerability in the Worldweaver DX Studio Player browser plugin (CVE-2009-2011). The exploit is designed for Windows systems running Internet Explorer or Firefox with the vulnerable plugin installed (version 3.0.29 or earlier). The module sets up a malicious HTTP server that serves a crafted HTML page and a .dxstudio file. When a victim visits the attacker's page, the vulnerable plugin processes the .dxstudio file, which uses scripting features to write a batch file to disk and execute it via shell.execute(), allowing arbitrary command execution. The exploit uses a VBS command stager to deliver the payload. The main entry point is the 'on_request_uri' method, which handles both the initial HTML delivery and the payload. The only endpoints are the HTTP server (attacker-controlled) and the temporary batch file created on the victim. The module is operational and leverages Metasploit's framework for payload handling and delivery.
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.