Loading vulnerability…
CVE-2025-34128 is a buffer overflow vulnerability in the X360 VideoPlayer ActiveX control, VideoPlayer.ocx, version 2.6. The flaw is triggered when the control processes overly long arguments supplied to the ConvertFile() method. Improper handling of the input length can corrupt memory, creating a condition in which attacker-controlled data may influence execution flow. In practical terms, a crafted call into the vulnerable ActiveX method can lead to arbitrary code execution in the context of the process hosting the control.
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.
This repository contains a single Metasploit module targeting a buffer overflow vulnerability (CVE-2025-34128) in the X360 VideoPlayer ActiveX control (VideoPlayer.ocx) on Windows. The exploit is delivered via a malicious web server, which serves a crafted HTML page and several JavaScript files (exploit.js, sprayer.js, informer.js, rop_builder.js) to the victim's Internet Explorer 10 browser. The vulnerability is triggered by passing an overly long value to the 'ConvertFile()' method of the ActiveX control, allowing the attacker to bypass ASLR/DEP and execute arbitrary code. The module is fully integrated into Metasploit, allowing for customizable payloads (such as Meterpreter) and automated exploitation. The main attack vector is browser-based, requiring the victim to visit a malicious page. The module references several endpoints for delivering exploit components and targets systems with the vulnerable ActiveX control installed. The structure is typical for a Metasploit browser exploit, with clear separation of payload delivery and exploit logic.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.