CVE-2000-1211

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 1%CVSS: Exploit: NoneExposed: 0

A fix is available — apply it.

Zope 2.2.0 through 2.2.4 does not properly perform security registration for legacy names of object constructors such as DTML method objects, which could allow attackers to perform unauthorized activities.

CVSS v3
EG Score
0.0(none)
EPSS
69.8%
KEV
Not listed

Published

December 16, 2000

Last Modified

June 16, 2026

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2000-12-13redhat
pipzopeghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
zope

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 2× in last 7d / 19× 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-11 08:22 UTCEPSS rescore
  2. 2026-07-08 15:08 UTCEPSS rescore
  3. 2026-07-04 06:26 UTCEPSS rescore
  4. 2026-07-02 14:00 UTCEPSS rescore
  5. 2026-06-29 14:02 UTCEPSS rescore
  6. 2026-06-28 14:02 UTCEPSS rescore
  7. 2026-06-27 03:04 UTCEPSS rescore
  8. 2026-06-24 14:01 UTCEPSS rescore
  9. 2026-06-23 21:29 UTCEPSS rescore
  10. 2026-06-22 14:22 UTCEPSS rescore
  11. 2026-06-21 01:56 UTCEPSS rescore
  12. 2026-06-19 19:22 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-18 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-14 23:13 UTCEPSS rescore
  18. 2026-06-13 22:56 UTCEPSS rescore
  19. 2026-06-12 23:07 UTCEPSS rescore
  20. 2026-06-11 13:55 UTCEPSS rescore
  21. 2026-06-10 22:13 UTCEPSS rescore
  22. 2026-06-10 13:17 UTCEPSS rescore
  23. 2026-06-08 14:13 UTCEPSS rescore
  24. 2026-06-07 15:21 UTCEPSS rescore
  25. 2026-06-06 13:44 UTCEPSS rescore
Show 29 more
  1. 2026-06-05 06:07 UTCEPSS rescore
  2. 2026-06-04 13:09 UTCEPSS rescore
  3. 2026-06-02 20:10 UTCEPSS rescore
  4. 2026-05-31 22:27 UTCEPSS rescore
  5. 2026-05-31 21:14 UTCEG score recompute
  6. 2026-05-31 21:14 UTCVendor advisory
  7. 2026-05-31 21:14 UTCGHSA enrichment
  8. 2026-05-31 00:13 UTCEPSS rescore
  9. 2026-05-31 00:13 UTCEPSS rescore
  10. 2026-05-29 13:40 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-27 13:37 UTCEPSS rescore
  16. 2026-05-27 13:37 UTCEPSS rescore
  17. 2026-05-26 13:41 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-24 16:42 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-21 22:38 UTCEPSS rescore
  25. 2026-05-20 22:36 UTCEPSS rescore
  26. 2026-05-20 11:20 UTCEPSS rescore
  27. 2026-05-20 11:20 UTCEPSS rescore
  28. 2026-05-18 21:29 UTCEPSS rescore
  29. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2000-1211?
CVE-2000-1211 is a none vulnerability published on December 16, 2000. Zope 2.2.0 through 2.2.4 does not properly perform security registration for legacy names of object constructors such as DTML method objects, which could allow attackers to perform unauthorized activities.
When was CVE-2000-1211 disclosed?
CVE-2000-1211 was first published in the National Vulnerability Database on December 16, 2000, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2000-1211 actively exploited?
CVE-2000-1211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 69.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2000-1211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2000-1211, 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-2000-1211

Explore →

Is Your Infrastructure Affected by CVE-2000-1211?

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