Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Zope DTML implementation Improper Authentication

CVE-2000-0062GHSA-wcwp-r3fj-mm3p

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI zope

    Affected
    >= 2.2.0, <= 2.2.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2000-0062: 2.24% estimated exploitation activity in the next 30 days; percentile 82.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The DTML implementation in the Z Object Publishing Environment (Zope) allows remote attackers to conduct unauthorized activities.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-wcwp-r3fj-mm3p

  2. Revision 1 · created ·

    Published from osv record GHSA-wcwp-r3fj-mm3p

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2000-0062

Advisory: Zope DTML implementation Improper Authentication
IDs: CVE-2000-0062, GHSA-wcwp-r3fj-mm3p
Record: https://patchnext.com/advisories/cve-2000-0062 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI zope: affected >= 2.2.0, <= 2.2.4

## Suggested inspection (read-only)
- `python -m pip show zope`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zope.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wcwp-r3fj-mm3p (OSV record GHSA-wcwp-r3fj-mm3p lists affected ranges: PyPI zope >=2.2.0 <=2.2.4)
- Verified: https://github.com/advisories/GHSA-wcwp-r3fj-mm3p (GitHub-reviewed advisory GHSA-wcwp-r3fj-mm3p lists affected ranges: PyPI zope >=2.2.0 <=2.2.4)

Commands are suggestions: review each one before running it.

Loading voting…