PatchTheCVECVE-2019-10682: django-nopassword before 5.0.0 stores cleartext secrets in the database.
CVE-2019-10682 is a high-severity flaw (CVSS 7.5) affecting django-nopassword. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
django-nopassword before 5.0.0 stores cleartext secrets in the database.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.2% (top 32%) |
| CISA exploited list | No |
| Weakness | CWE-312 |
| Published | 2020-03-18 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2019-10682?
django-nopassword: upgrade to 5.0.0. Exact commands for each OS are on this page.
Is CVE-2019-10682 being exploited?
CVE-2019-10682 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2019-10682 affect?
CVE-2019-10682 affects django-nopassword. Severity is high (CVSS 7.5). django-nopassword before 5.0.0 stores cleartext secrets in the database.
How urgent is CVE-2019-10682?
Priority 48/100. High severity; Remotely exploitable, no login, no user action