NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2020-7941 — plone

CRITICAL

CVE-2020-7941 is a critical-severity (CVSS 9.8) vulnerability in plone. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Plone Unauthenticated Write Vulnerability

Also known asGHSA-w6g9-xccc-347hPYSEC-2020-90PYSEC-2026-459
Published
Updated
Affected
2 pkgs
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
0.12%1.00%1.88%2.77%0.6%2.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐍plone🐍plone-app-contenttypes

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

A privilege escalation issue in plone.app.contenttypes in Plone 4.3 through 5.2.1 allows users to PUT (overwrite) some content without needing write permission.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
🐍PyPIplone≥ 4.3No fix
🐍PyPIplone-app-contenttypesall versionsNo fix

Affected Products

1 product · 1 configurations
Application
ploneplone
≥ 4.3.0 && ≤ 5.2.1
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

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

  3. Mitigate without a patch

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

A privilege escalation issue in plone.app.contenttypes in Plone 4.3 through 5.2.1 allows users to PUT (overwrite) some content without needing write permission.
O3 Security · Impact-Aware SCA

Is CVE-2020-7941 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2020-7941: plone PrivEsc (Critical 9.8)