Plone allows weak passwords

published 2020-01-23 6 y ago modified 2026-06-17 4 mo ago also GHSA-cw58-gpgw-hwx2 , PYSEC-2020-89 , EUVD-2020-0147

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

pypi plone 4.3.20, 5.1.7, 5.2.1, 5.2.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-7940 updated 2026-11-07 cvss 7.5

plone: missing password strength checks on some forms

Red Hat Enterprise Linux 5 conga
affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	plone	>=4.3, <4.3.20 >=5.0rc1, <5.1.7 >=5.2.0, <5.2.2 >=4.3, <5.2.1	4.3.20 5.1.7 5.2.2 5.2.1

Classification

Weakness

CWE-521 Weak Password Requirements

References

plone.org /security/hotfix/20200121
web, vendor-advisory
plone.org /security/hotfix/20200121/password-strength-checks-were-not-always-checked
web, vendor-advisory
openwall.com /lists/oss-security/2020/01/22/1
web, mailing-list, third-party-advisory
openwall.com /lists/oss-security/2020/01/24/1
mailing-list, web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2020-7940
advisory
github.com /plone/Plone
package
github.com /pypa/advisory-database/tree/main/vulns/plone/PYSEC-2020-89.yaml
web
github.com /advisories/GHSA-cw58-gpgw-hwx2
advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary