CVE-2011-3587

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS: 79%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Unspecified vulnerability in Zope 2.12.x and 2.13.x, as used in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2, allows remote attackers to execute arbitrary commands via vectors related to the p_ class in OFS/misc_.py and the use of Python modules.

CVSS v3
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses intrinsic severity with real-world exploitation and automatability, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
99.5%
KEV
Not listed

Published

October 10, 2011

Last Modified

April 29, 2026

References (16)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
zope22.13.0 ... 2.13.9 (10 versions)2.13.10—

Data Freshness Timeline

(refreshed 5× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:05 UTCEG score recompute▼ 7.90
  2. 2026-07-23 00:09 UTCEG score recompute▲ 7.90
  3. 2026-07-22 21:48 UTCEG score recompute▼ 9.00
  4. 2026-07-22 14:03 UTCEPSS rescore
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-15 16:54 UTCEPSS rescore
  7. 2026-07-15 16:54 UTCEPSS rescore
  8. 2026-07-11 08:22 UTCEPSS rescore
  9. 2026-07-11 08:22 UTCEPSS rescore
  10. 2026-07-05 02:26 UTCEPSS rescore
  11. 2026-07-01 15:02 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-30 23:19 UTCEPSS rescore
  15. 2026-06-29 14:02 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-28 04:52 UTCEPSS rescore
  18. 2026-06-25 13:46 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-24 14:02 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-19 19:22 UTCEPSS rescore
  24. 2026-06-19 19:22 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 28 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-17 17:49 UTCEPSS rescore
  3. 2026-06-15 17:44 UTCEPSS rescore
  4. 2026-06-13 22:57 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-11 13:56 UTCEPSS rescore
  7. 2026-06-10 13:17 UTCEPSS rescore
  8. 2026-06-08 14:14 UTCEPSS rescore
  9. 2026-06-08 14:14 UTCEPSS rescore
  10. 2026-06-05 22:44 UTCEPSS rescore
  11. 2026-06-02 20:10 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 22:28 UTCEPSS rescore
  15. 2026-05-31 00:14 UTCEPSS rescore
  16. 2026-05-31 00:14 UTCEPSS rescore
  17. 2026-05-29 06:38 UTCEG score recompute
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-26 13:41 UTCEPSS rescore
  22. 2026-05-26 13:41 UTCEPSS rescore
  23. 2026-05-24 16:43 UTCEPSS rescore
  24. 2026-05-20 22:37 UTCEPSS rescore
  25. 2026-05-20 22:37 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-18 21:29 UTCEPSS rescore
  28. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-18262✓ verified
    First seen Dec 21, 2011

    Plone and Zope - Remote Command Execution

    Open source ↗
  • Metasploitexploit/multi/http/plone_popen2✓ verified
    First seen Oct 4, 2011

    Plone and Zope XMLTools Remote Command Execution

    Open source ↗

Frequently asked(4)

What is CVE-2011-3587?
CVE-2011-3587 is a none vulnerability published on October 10, 2011. Unspecified vulnerability in Zope 2.12.x and 2.13.x, as used in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2, allows remote attackers to execute arbitrary commands via vectors related to the p class in OFS/misc.py and the use of Python modules.
When was CVE-2011-3587 disclosed?
CVE-2011-3587 was first published in the National Vulnerability Database on October 10, 2011, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-3587 actively exploited?
CVE-2011-3587 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2011-3587?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-3587, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2011-3587

Explore →

Is Your Infrastructure Affected by CVE-2011-3587?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs