django-nopassword vulnerabilities and fixes

Recent CVEs affecting django-nopassword, with upgrade or downgrade steps. 1 tracked.

Also searched as: django nopassword.

django-nopassword has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-03-18. Highest priority: CVE-2019-10682 (score 48/100).

• CVE-2019-10682 HIGH 7.5 UPGRADE django-nopassword before 5.0.0 stores cleartext secrets in the database.

FAQ

How do I fix django-nopassword vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is django-nopassword being exploited right now?

None of the tracked django-nopassword CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which django-nopassword CVE should I patch first?

CVE-2019-10682 currently ranks highest (48/100): django-nopassword before 5.0.0 stores cleartext secrets in the database..

← Back to latest CVEs