CVE-2020-7940 — plone
HIGHCVE-2020-7940 is a high-severity (CVSS 7.5) CWE-521 vulnerability in plone. A fix is available for plone — see the affected versions and patch details below.
Plone allows weak passwords
EPSS Exploitation Probability
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
plone🐍plone🐍ploneReal-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
Missing password strength checks on some forms in Plone 4.3 through 5.2.0 allow users to set weak passwords, leading to easier cracking.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | plone | ≥ 4.3&&< 4.3.20 | 4.3.20pip install --upgrade 'plone==4.3.20' |
| 🐍PyPI | plone | ≥ 5.0rc1&&< 5.1.7 | 5.1.7pip install --upgrade 'plone==5.1.7' |
| 🐍PyPI | plone | ≥ 5.2.0&&< 5.2.2 | 5.2.2pip install --upgrade 'plone==5.2.2' |
Affected Products
ploneploneDetection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update plone to 4.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7940 is resolved across your whole dependency graph.
Workarounds
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.
Frequently Asked Questions
Is CVE-2020-7940 in your dependencies?
Find it across PyPI, including transitive dependencies.