CVE-2023-32061 json
Discourse Topic Creation Page Allows iFrame Tag without Restrictions
published 2023-06-13 3 y ago modified 2026-09-08 2 mo ago also BIT-discourse-2023-32061 , EUVD-2023-36346 , GHSA-prx4-49m8-874g
- cvss
- 5.4
- 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 29%
- public exploits
- 0
- none known
Summary
Discourse is an open source discussion platform. Prior to version 3.0.4 of the `stable` branch and version 3.1.0.beta5 of the `beta` and `tests-passed` branches, the lack of restrictions on the iFrame tag makes it easy for an attacker to exploit the vulnerability and hide subsequent comments from other users. This issue is patched in version 3.0.4 of the `stable` branch and version 3.1.0.beta5 of the `beta` and `tests-passed` branches. There are no known workarounds.
Patch / fix
- bitnami discourse 3.0.4
- discourse discourse 3.0.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 22 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | discourse | <3.0.4 |
3.0.4 |
Affected products
- discourse discourse
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/discourse/discourse/security/advisories/GHSA-prx4-49m8-874g
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-32061
web
Sources
- CVE List CVE-2023-32061
- NVD CVE-2023-32061
- OSV BIT-discourse-2023-32061
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.