How severe is CVE-2000-1211?

No CVSS score has been assigned to CVE-2000-1211 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2000-1211?

CVE-2000-1211 affects the following packages: zope (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2000-1211?

The records we use list no patched version of zope for CVE-2000-1211. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2000-1211 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zope, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2000-1211 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2000-1211 actively exploited in the wild?

No public exploit code has been indexed for CVE-2000-1211 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2000-1211?

CVE-2000-1211 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2000-1211 published, and has it been updated?

CVE-2000-1211 was published on April 30, 2022 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2000-1211 — zope

CVE-2000-1211 is a security vulnerability in zope. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Zope does not properly perform security registration for legacy names

Also known asPYSEC-2026-759

Published

Apr 30, 2022

Updated

Jul 6, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍zope

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`zope`	≥ 2.2.0	No fix

Affected Products

1 product · 11 configurations

Application

zopezope

11 versions

2.2.02.2.0a12.2.0b12.2.0b22.2.0b32.2.0b42.2.12.2.1b12.2.22.2.32.2.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zope, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of zope for CVE-2000-1211. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red Hat

RHSA-2000:125Red Hat Powertools 6.2

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2000-1211 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works