CVE-2024-49765 json
Bypass of Discourse Connect using other login paths if enabled in Discourse
published last yr. modified 2mo ago also BIT-discourse-2024-49765 , EUVD-2024-43816 , GHSA-v8rf-pvgm-xxf2
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
Discourse is an open source platform for community discussion. Sites that are using discourse connect but still have local logins enabled could allow attackers to bypass discourse connect to create accounts and login. This problem is patched in the latest version of Discourse. Users unable to upgrade who are using discourse connect may disable all other login methods as a workaround.
Patch / fix
- bitnami discourse 3.3.3
- discourse discourse 3.3.3, 3.4.0.beta4
Is CVE-2024-49765 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | discourse | <3.3.3 |
3.3.3 |
Affected products
- discourse discourse
Classification
- Weakness
-
- CWE-359 Exposure of Private Personal Information to an Unauthorized Actor
References
-
github.com
/discourse/discourse/security/advisories/GHSA-v8rf-pvgm-xxf2
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-49765
web
Sources
- CVE List CVE-2024-49765
- NVD CVE-2024-49765
- OSV BIT-discourse-2024-49765
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.