Loading vulnerability…
Adobe RoboHelp Server 8 contains an unrestricted file upload vulnerability in the RoboHelpServer Servlet (robohelp/server). Remote attackers can upload arbitrary files, such as .jsp web shells, during a PUBLISH action. The uploaded file is placed in the robohelp/robo/reserved/web directory under a sessionid subdirectory, and can then be accessed and executed directly, leading to remote code execution on the server.
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 module targeting Adobe RoboHelp Server 8 on Windows (CVE-2009-3068). The exploit leverages an authentication bypass to upload and execute arbitrary code as a JSP file via a crafted POST request to the /robohelp/server endpoint. Upon successful upload, the module accesses the uploaded JSP file through a secondary HTTP GET request to execute the payload, typically resulting in remote code execution (e.g., a shell). The module is written in Ruby and is structured according to Metasploit conventions, with the main exploit logic in the 'exploit' method. The exploit is operational, providing a working payload mechanism, and is suitable for use in penetration testing scenarios where the target is known to be vulnerable.
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.