CVE-2020-7940: Weak Password Strength Checks in Plone

plone Updated 02 Oct 2025

Summary

23/01/2020
Yes i
High
7.5

CVE-2020-7940: 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. Affects plone versions >= 4.3, < 5.2.1. Fixed in 5.2.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Plone is an open-source content management system built on top of the Zope application server. It provides a robust and flexible platform for creating and managing websites, intranets, and web applications. Plone is widely used due to its security features and extensibility. However, versions 4.3 through 5.2.0 of Plone suffer from a vulnerability that allows users to set weak passwords without proper strength checks.

Vulnerability Detail

The vulnerability in Plone arises from the absence of password strength checks on certain forms. This oversight enables users to choose weak passwords, which can be easily cracked by attackers. Weak passwords pose a significant security risk as they can be exploited to gain unauthorized access to user accounts, compromising sensitive information and potentially leading to further attacks.

How To Fix

Latest published version: 6.2.2 as of 23 Oct 2026

pip install --upgrade "plone==6.2.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.2.1

This is the first release that contains the fix.

pip install --upgrade "plone==5.2.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, as a general best practice, users can manually enforce strong password policies by educating and encouraging users to choose passwords that meet certain complexity requirements. This can include a combination of uppercase and lowercase letters, numbers, and special characters. Additionally, implementing multi-factor authentication can provide an extra layer of security.

Conclusion

In conclusion, Plone versions 4.3 through 5.2.0 are vulnerable to weak password strength checks, allowing users to set weak passwords that can be easily cracked. To address this issue, it is crucial to upgrade to Plone version 5.2.1 or later, which includes the necessary password strength checks. Additionally, enforcing strong password policies and implementing multi-factor authentication can further enhance the security of the system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

FAQ

The impact of this vulnerability is that users can set weak passwords, making it easier for attackers to crack them and gain unauthorized access to user accounts.

Versions 4.3 through 5.2.0 of Plone are affected by this vulnerability.

There are no known exploits for this vulnerability at the moment. However, it is crucial to address this issue promptly to prevent potential attacks.

Yes, a patch is available in Plone version 5.2.1. It includes the necessary password strength checks to mitigate this vulnerability.

While upgrading to the latest version of Plone is the recommended solution, implementing strong password policies and multi-factor authentication can provide additional layers of security against password cracking attempts.

Related vulnerabilities

Recent vulnerabilities recorded for plone.

How To Fix

Latest published version: 6.2.2 as of 23 Oct 2026

pip install --upgrade "plone==6.2.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.2.1

This is the first release that contains the fix.

pip install --upgrade "plone==5.2.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback