CVE-2019-1020017: Discourse before 2.3.0 and 2.4.x before 2.4.0.beta3 lacks a confirmation screen when logging in via a user-api

Q: How do I fix CVE-2019-1020017?

discourse: upgrade to 2.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2019-1020017 being exploited?

CVE-2019-1020017 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-2019-1020017 affect?

CVE-2019-1020017 affects discourse. Severity is medium (CVSS 5.3). Discourse before 2.3.0 and 2.4.x before 2.4.0.beta3 lacks a confirmation screen when logging in via a user-api OTP.

Q: How urgent is CVE-2019-1020017?

Priority 38/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2019-1020017 is a medium-severity flaw (CVSS 5.3) affecting discourse. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Discourse before 2.3.0 and 2.4.x before 2.4.0.beta3 lacks a confirmation screen when logging in via a user-api OTP.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Published	2019-07-29
Last modified	2026-06-17

Publisher (CNA): DWF · Vendor: discourse

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

Am I affected?

Timeline

2019-07-29 13:15 UTCPublished CVE record published
2026-06-17 02:10 UTCUpdated Record last modified

discourse discourse UPGRADE

Affected: < 2.3.0 · 2.4.0 beta1 · 2.4.0 beta2

Fixed in: 2.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy discourse || rpm -q discourse || discourse --version

2. UPGRADE to 2.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade discourse

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade discourse

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-2019-1020017?

discourse: upgrade to 2.3.0. Exact commands for each OS are on this page.

Is CVE-2019-1020017 being exploited?

CVE-2019-1020017 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-1020017 affect?

CVE-2019-1020017 affects discourse. Severity is medium (CVSS 5.3). Discourse before 2.3.0 and 2.4.x before 2.4.0.beta3 lacks a confirmation screen when logging in via a user-api OTP.

How urgent is CVE-2019-1020017?

Priority 38/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-59337 MEDIUM 6.8 UPGRADE Discourse is an open-source community discussion platform
CVE-2025-58055 MEDIUM 4.3 UPGRADE Discourse is an open-source community discussion platform
CVE-2025-58054 LOW 3.5 UPGRADE Discourse is an open-source community discussion platform
CVE-2025-61598 MEDIUM 5.3 UPGRADE Discourse is an open source discussion platform
CVE-2026-27481 MEDIUM 5.3 UPGRADE Discourse is an open-source discussion platform

References

← Back to latest CVEs