CVE-2022-31184 json
Email activation route can be abused by spammers in Discourse
published 2022-08-01 4 y ago modified 2026-09-08 2 mo ago also BIT-discourse-2022-31184 , EUVD-2022-52780 , GHSA-m5w9-8gp8-2hrf
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Discourse is the an open source discussion platform. In affected versions an email activation route can be abused to send mass spam emails. A fix has been included in the latest stable, beta and tests-passed versions of Discourse which rate limits emails. Users are advised to upgrade. Users unable to upgrade should manually rate limit email.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | discourse | <=2.8.6 |
no fix listed |
Affected products
- discourse discourse
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/discourse/discourse/commit/af1cb735db7fb73217b85d22dbadd1bc824ac0b0
patch, third-party-advisory, advisory
-
github.com
/discourse/discourse/security/advisories/GHSA-m5w9-8gp8-2hrf
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-31184
web
Sources
- CVE List CVE-2022-31184
- NVD CVE-2022-31184
- OSV BIT-discourse-2022-31184
Fencer Vulns 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.