CVE-2020-15105: Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (ba

Q: How do I fix CVE-2020-15105?

django two-factor authentication: upgrade to 1.12. Exact commands for each OS are on this page.

Q: Is CVE-2020-15105 being exploited?

CVE-2020-15105 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-15105 affect?

CVE-2020-15105 affects django two-factor authentication. Severity is medium (CVSS 5.4). Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they c

Q: How urgent is CVE-2020-15105?

Priority 32/100. No elevated risk signals yet.

Routine

MEDIUM 5.4UPGRADE

CVE-2020-15105 is a medium-severity flaw (CVSS 5.4) affecting django two-factor authentication. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begi

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-312
Published	2020-07-10
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: django two-factor authentication project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-07-10 21:15 UTCPublished CVE record published
2026-06-17 02:56 UTCUpdated Record last modified

django two-factor authentication project django two-factor authentication UPGRADE

Affected: < 1.12

Fixed in: 1.12

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy django-two-factor-authentication || rpm -q django-two-factor-authentication || django-two-factor-authentication --version

2. UPGRADE to 1.12 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-two-factor-authentication

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-two-factor-authentication

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2020-15105?

django two-factor authentication: upgrade to 1.12. Exact commands for each OS are on this page.

Is CVE-2020-15105 being exploited?

CVE-2020-15105 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-2020-15105 affect?

CVE-2020-15105 affects django two-factor authentication. Severity is medium (CVSS 5.4). Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they c

How urgent is CVE-2020-15105?

Priority 32/100. No elevated risk signals yet.

Software pages

Django vulnerabilities

References

← Back to latest CVEs