VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

zope2: vulnerability history, versions and safety

zope2 is a package in the PyPI ecosystem. Vulert records 20 vulnerabilities for it across 120 releases, from Jul 2006 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded H5 M3 L1 U11
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 06 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all zope2 vulnerabilities

Vulert verdict on zope2 4.0.0 i

Updated on 23 Oct 2026

Careful: 4.0.0 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 52/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.0.0 — affected i
  • Vulnerabilities on record 20 over 19 years · 5 in the last year i
  • Latest disclosure 06 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 3 i
  • Depended on by 99 packages i
  • Last release 89 months ago i
  • Licence ZPL-2.1 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for zope2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.13.30 14 Feb 2020 U2 ZPL-2.1 No Details →
4.0.0 10 May 2019 M1 U2 ZPL-2.1 No Details →
2.13.29 09 Feb 2019 U2 ZPL-2.1 No Details →
2.13.28 23 Apr 2018 U2 ZPL-2.1 No Details →
2.13.27 27 Jan 2018 U2 ZPL-2.1 No Details →
4.0.0b1 18 Sep 2017 M1 U2 ZPL-2.1 No Details →
4.0.0a6 01 Jun 2017 M1 U2 ZPL-2.1 No Details →
4.0.0a5 28 May 2017 M1 U2 ZPL-2.1 No Details →
4.0.0a4 12 May 2017 M1 U2 ZPL-2.1 No Details →
4.0.0a3 03 May 2017 M1 U2 ZPL-2.1 No Details →
2.13.26 20 Feb 2017 U2 ZPL-2.1 No Details →
2.13.25 13 Jan 2017 U2 ZPL-2.1 No Details →
4.0.0a2 09 Sep 2016 M1 U2 ZPL-2.1 No Details →
4.0.0a1 22 Jul 2016 M1 U2 ZPL-2.1 No Details →
2.13.24 29 Feb 2016 U2 ZPL-2.1 No Details →
2.13.23 29 Jun 2015 U2 ZPL-2.1 No Details →
2.13.22 19 Feb 2014 U2 ZPL-2.1 No Details →
2.12.28 16 Jul 2013 H3 U5 ZPL-2.1 No Details →
2.13.21 16 Jul 2013 U2 ZPL-2.1 No Details →
2.13.20 01 May 2013 U2 ZPL-2.1 No Details →
2.12.27 01 May 2013 H3 U5 ZPL-2.1 No Details →
2.13.19 31 Oct 2012 U2 ZPL-2.1 No Details →
2.12.26 31 Oct 2012 H3 U5 ZPL-2.1 No Details →
2.13.18 18 Sep 2012 H3 U5 ZPL-2.1 No Details →
2.12.25 18 Sep 2012 H3 U5 ZPL-2.1 No Details →
2.13.17 09 Sep 2012 H3 U5 ZPL-2.1 No Details →
2.12.24 09 Sep 2012 H3 U5 ZPL-2.1 No Details →
2.13.16 11 Aug 2012 H3 U5 ZPL-2.1 No Details →
2.13.15 22 Jun 2012 H3 U5 ZPL-2.1 No Details →
2.13.14 31 May 2012 H3 U5 ZPL-2.1 No Details →
2.13.13 20 Feb 2012 H3 U5 ZPL-2.1 No Details →
2.12.23 20 Feb 2012 H3 U5 ZPL-2.1 No Details →
2.13.12 18 Jan 2012 H3 U5 ZPL-2.1 No Details →
2.12.22 18 Jan 2012 H3 U5 ZPL-2.1 No Details →
2.13.11 12 Dec 2011 H3 U6 ZPL-2.1 No Details →
2.12.21 12 Dec 2011 H3 U6 ZPL-2.1 No Details →
2.13.10 04 Oct 2011 H3 U7 ZPL-2.1 No Details →
2.12.20 04 Oct 2011 H4 U7 ZPL-2.1 No Details →
2.13.9 20 Aug 2011 H3 U8 ZPL-2.1 No Details →
2.13.8 28 Jun 2011 H3 U8 ZPL-2.1 No Details →
2.12.19 28 Jun 2011 H5 U8 ZPL-2.1 No Details →
2.13.7 08 May 2011 H3 U9 ZPL-2.1 No Details →
2.12.18 08 May 2011 H5 U9 ZPL-2.1 No Details →
2.13.6 03 Apr 2011 H3 U9 ZPL-2.1 No Details →
2.12.17 03 Apr 2011 H5 U9 ZPL-2.1 No Details →
2.13.5 23 Feb 2011 H3 U9 ZPL-2.1 No Details →
2.12.16 23 Feb 2011 H5 U9 ZPL-2.1 No Details →
2.13.4 06 Feb 2011 H3 U9 ZPL-2.1 No Details →
2.13.3 06 Feb 2011 H3 U9 ZPL-2.1 No Details →
2.12.15 06 Feb 2011 H5 U9 ZPL-2.1 No Details →
2.13.2 19 Jan 2011 H3 U9 ZPL-2.1 No Details →
2.13.1 07 Dec 2010 H3 U9 ZPL-2.1 No Details →
2.12.14 07 Dec 2010 H5 U9 ZPL-2.1 No Details →
2.12.13 06 Nov 2010 H5 U9 ZPL-2.1 No Details →
2.13.0 05 Nov 2010 H3 U9 ZPL-2.1 No Details →
2.13.0rc1 28 Oct 2010 H3 M1 U5 ZPL-2.1 No Details →
2.13.0b1 09 Oct 2010 H3 U6 ZPL-2.1 No Details →
2.12.12 02 Oct 2010 H5 U9 ZPL-2.1 No Details →
2.13.0a4 09 Sep 2010 H3 U6 ZPL-2.1 No Details →
2.12.11 09 Sep 2010 H5 U9 ZPL-2.1 No Details →
2.13.0a3 04 Aug 2010 H3 U6 ZPL-2.1 No Details →
2.12.10 20 Jul 2010 H5 U9 ZPL-2.1 No Details →
2.13.0a2 13 Jul 2010 H3 U6 ZPL-2.1 No Details →
2.12.9 13 Jul 2010 H5 U9 ZPL-2.1 No Details →
2.13.0a1 25 Jun 2010 H3 U6 ZPL-2.1 No Details →
2.12.8 25 Jun 2010 H5 U9 ZPL-2.1 No Details →
2.12.7 13 Jun 2010 H5 U9 ZPL-2.1 No Details →
2.12.6 17 May 2010 H5 U9 ZPL-2.1 No Details →
2.12.5 24 Apr 2010 H5 U9 ZPL-2.1 No Details →
2.12.4 05 Apr 2010 H5 M1 U10 ZPL-2.1 No Details →
2.12.3 13 Jan 2010 H5 M1 U10 ZPL-2.1 No Details →
2.12.2 22 Dec 2009 H5 M1 U11 ZPL-2.1 No Details →
2.12.1 02 Nov 2009 H5 M1 U11 ZPL-2.1 No Details →
2.12.0 30 Sep 2009 H5 M1 U11 ZPL-2.1 No Details →
2.12.0rc1 04 Sep 2009 H4 M2 U8 ZPL-2.1 No Details →
2.12.0b4 06 Aug 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0b3 14 Jul 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0b2 26 May 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0b1 05 May 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0a4 24 Apr 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0a3 19 Apr 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0a2 19 Apr 2009 H4 M1 U8 ZPL-2.1 No Details →
2.12.0a1 26 Feb 2009 H4 M2 U8 ZPL-2.1 No Details →
2.12.0-py2.4-win32 — H5 M2 U10 — No Details →
2.12.0-py2.5-win32 — H5 M2 U10 — No Details →
2.12.0-py2.6-win-amd64 — H5 M2 U10 — No Details →
2.12.0-py2.6-win32 — H5 M2 U10 — No Details →
2.12.0.a1-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0.a1-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0.a1-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0a2-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0a2-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0a2-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0a3-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0a3-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0a3-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0b1-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0b1-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0b1-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0b2-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0b2-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0b2-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0b3-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0b3-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0b3-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0b4-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0b4-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0b4-py2.6-win32 — H4 M2 U8 — No Details →
2.12.0c1-py2.4-win32 — H4 M2 U8 — No Details →
2.12.0c1-py2.5-win32 — H4 M2 U8 — No Details →
2.12.0c1-py2.6-win32 — H4 M2 U8 — No Details →
2.12.1-py2.4-win32 — H5 M2 U10 — No Details →
2.12.1-py2.5-win32 — H5 M2 U10 — No Details →
2.12.1-py2.6-win-amd64 — H5 M2 U10 — No Details →
2.12.1-py2.6-win32 — H5 M2 U10 — No Details →
2.12.10-py2.6-win-amd64 — H5 M1 U9 — No Details →
2.12.10-py2.6-win32 — H5 M1 U9 — No Details →
2.12.11-py2.6-win-amd64 — H5 M1 U9 — No Details →
2.12.11-py2.6-win32 — H5 M1 U9 — No Details →
2.12.12-py2.6-win-amd64 — H5 M1 U9 — No Details →

The newest 120 of 182 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2006 2
  • 2014 4
  • 2018 5
  • 2022 4
  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 20 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for zope2

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2012-5507: Password Disclosure Vulnerability in Plone and Zope2 7.5 high 2.13.19 23 Jul 2018
CVE-2012-6661: Vulnerability in Plone and Zope2 7.5 high 2.13.19 23 Jul 2018
CVE-2012-5486: HTTP header injection in Plone and Zope2 7.5 high 2.13.19 23 Jul 2018
CVE-2012-5489: Vulnerability in Plone and Zope2 6.5 high 2.12.21 23 Jul 2018
CVE-2009-5145: Zope2 Cross-site Scripting (XSS) Vulnerability in ZMI Pages 6.1 medium 2.12.5 02 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About zope2

Is zope2 safe to use?

Vulert records 20 vulnerabilities for zope2 in PyPI: 0 critical, 5 high, 3 medium and 1 low, plus 11 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is zope2's Vulert package health score?

Vulert scores zope2 52/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of zope2 affected?

Yes. 4.0.0, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of zope2 should I use?

4.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does zope2 have?

20 vulnerabilities are recorded for zope2 in the PyPI ecosystem: 0 critical, 5 high, 3 medium and 1 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new zope2 vulnerabilities disclosed?

5 vulnerabilities were recorded for zope2 in the last 12 months, and the oldest entry in this database dates to 07 Jul 2006. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of zope2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor zope2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the zope2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.