CVE-2011-3587 is an unspecified command execution vulnerability in Zope 2.12.x and 2.13.x, including deployments as used in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2. The issue is related to the p_ class in OFS/misc_.py and the use of Python modules. A remote attacker can exploit this flaw to execute arbitrary commands on the affected system. The available information indicates that the vulnerability stems from unsafe handling of functionality associated with Python module access or invocation within that component.
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 (modules/exploits/multi/http/plone_popen2.rb) targeting a remote command execution vulnerability (CVE-2011-3587) in Zope 2.12.x/2.13.x as used in Plone 4.0.x-4.2a2. The exploit works by sending a crafted HTTP POST request to the vulnerable endpoint '/p_/webdav/xmltools/minidom/xml/sax/saxutils/os/popen2' on the target server (default port 8080), with the attacker's command as a POST parameter. The module supports generic command payloads and is fully integrated into the Metasploit framework, allowing for payload customization and automated exploitation. The code is mature and weaponized, providing reliable remote code execution on affected systems. The repository is structured as a single Ruby file, following standard Metasploit module conventions.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.