Foxit Reader versions 2.3 before Build 3902 and 3.0 before Build 1506 (including builds 1120 and 1301) fail to require user confirmation before executing dangerous actions defined in a PDF file, such as the 'Open/Execute a file' action. This allows remote attackers to craft malicious PDF files that, when opened, can execute arbitrary programs on the victim's system without any user interaction. The vulnerability is due to insufficient authorization checks in the handling of PDF action triggers.
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 auxiliary module targeting an authorization bypass vulnerability in Foxit Reader build 1120 (CVE-2009-0836). The module generates a malicious PDF file that, when opened by a victim using the vulnerable version of Foxit Reader, will execute an arbitrary command on the victim's system without confirmation. The default command is to launch the Windows calculator, but this can be customized. The exploit leverages the PDF /Launch action to trigger command execution. The code is written in Ruby and is structured as a typical Metasploit module, with options to specify the command to execute and the output filename for the malicious PDF. The main attack vector is through a crafted file (PDF), and the primary fingerprintable endpoints are the default command path and the generated PDF filename.
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.