Discourse 2.8.0 Beta 10
Approved changes feed: RSS · Atom
cpe:2.3:a:discourse:discourse:2.8.0:beta10:*:*:*:*:*:*
part: a version: 2.8.0 update: beta10
| Vendor | Discourse (2d3c125b-857a-5933-b846-ed7f9d5e0225) |
|---|---|
| Product | Discourse (4347364d-ae10-5ab6-a9ec-6e7dcaf78dd8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/discourse/discourse |
purl2cpe | 2026-06-01 10:13:03.518925 |
pkg:rpm/opensuse/discourse |
purl2cpe | 2026-06-01 10:13:03.518927 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-21684 |
vulnerable | 2026-06-03 14:46:13.338206 |
User can bypass approval when invited to Discourse
MEDIUM (4.3)
Discourse is an open source discussion platform. Versions prior to 2.7.13 in `stable`, 2.8.0.beta11 in `beta`, and 2.8.0.beta11 in `tests-passed` allow some users to log in to a community before they should be able to do so. A user invited via email to a forum with `must_approve_users` enabled is going to be automatically logged in, bypassing the check that does not allow unapproved users to sign in. They will be able to do everything an approved user can do. If they logout, they cannot log back in. This issue is patched in the `stable` version 2.7.13, `beta` version 2.8.0.beta11, and `tests-passed` version 2.8.0.beta11. One may disable invites as a workaround. Administrators can increase `min_trust_level_to_allow_invite` to reduce the attack surface to more trusted users.
Published: 2022-01-13T21:05:11.000Z
Updated: 2025-04-23T19:12:19.304Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-21678 |
vulnerable | 2026-06-03 14:46:13.321304 |
User's bio visible even if profile is restricted in Discourse
MEDIUM (4.3)
Discourse is an open source discussion platform. Prior to version 2.8.0.beta11 in the `tests-passed` branch, version 2.8.0.beta11 in the `beta` branch, and version 2.7.13 in the `stable` branch, the bios of users who made their profiles private were still visible in the `<meta>` tags on their users' pages. The problem is patched in `tests-passed` version 2.8.0.beta11, `beta` version 2.8.0.beta11, and `stable` version 2.7.13 of Discourse.
Published: 2022-01-13T17:30:12.000Z
Updated: 2025-04-23T19:13:09.575Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-21677 |
vulnerable | 2026-06-03 14:46:13.320581 |
Group advanced search option may leak group and group's members visibility
MEDIUM (4.3)
Discourse is an open source discussion platform. Discourse groups can be configured with varying visibility levels for the group as well as the group members. By default, a newly created group has its visibility set to public and the group's members visibility set to public as well. However, a group's visibility and the group's members visibility can be configured such that it is restricted to logged on users, members of the group or staff users. A vulnerability has been discovered in versions prior to 2.7.13 and 2.8.0.beta11 where the group advanced search option does not respect the group's visibility and members visibility level. As such, a group with restricted visibility or members visibility can be revealed through search with the right search option. This issue is patched in `stable` version 2.7.13, `beta` version 2.8.0.beta11, and `tests-passed` version 2.8.0.beta11 versions of Discourse. There are no workarounds aside from upgrading.
Published: 2022-01-14T16:45:17.000Z
Updated: 2025-04-23T19:12:05.254Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-21642 |
vulnerable | 2026-06-03 14:46:13.248864 |
Exposure of whisper participants in discourse
MEDIUM (4.3)
Discourse is an open source platform for community discussion. In affected versions when composing a message from topic the composer user suggestions reveals whisper participants. The issue has been patched in stable version 2.7.13 and beta version 2.8.0.beta11. There is no workaround for this issue and users are advised to upgrade.
Published: 2022-01-05T19:05:10.000Z
Updated: 2025-04-23T19:14:48.196Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.