Approved changes feed: RSS · Atom

cpe:2.3:a:discourse:discourse:3.2.0:beta2:*:*:beta:*:*:*

part: a version: 3.2.0 update: beta2

VendorDiscourse (2d3c125b-857a-5933-b846-ed7f9d5e0225)
ProductDiscourse (4347364d-ae10-5ab6-a9ec-6e7dcaf78dd8)
Edition*
Language*
Software editionbeta
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/discourse/discourse purl2cpe 2026-06-01 10:13:03.594652
pkg:rpm/opensuse/discourse purl2cpe 2026-06-01 10:13:03.594653

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-32376 vulnerable 2026-06-03 15:00:40.694062 Discourse DM limits aren’t always properly enforced
Discourse is an open-source discussion platform. Prior to versions 3.4.3 on the stable branch and 3.5.0.beta3 on the beta branch, the users limit for a DM can be bypassed, thus giving the ability to potentially create a DM with every user from a site in it. This issue has been patched in stable version 3.4.3 and beta version 3.5.0.beta3.
Published: 2025-04-30T14:55:21.473Z
Updated: 2025-04-30T15:08:52.268Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-24748 vulnerable 2026-06-03 14:55:05.654606 Disclosure of the existence of secret subcategories in Discourse
MEDIUM (5.3)
Discourse is an open source platform for community discussion. In affected versions an attacker can learn that a secret subcategory exists under a public category which has no public subcategories. The issue is patched in the latest stable, beta and tests-passed version of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Published: 2024-03-15T19:15:17.121Z
Updated: 2024-08-27T19:43:50.659Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-23834 vulnerable 2026-06-03 14:55:04.751526 Discourse improperly sanitized user input leads to XSS
MEDIUM (6.3)
Discourse is an open-source discussion platform. Improperly sanitized user input could lead to an XSS vulnerability in some situations. This vulnerability only affects Discourse instances which have disabled the default Content Security Policy. The vulnerability is patched in 3.1.5 and 3.2.0.beta5. As a workaround, ensure Content Security Policy is enabled and does not include `unsafe-inline`.
Published: 2024-01-30T21:31:35.617Z
Updated: 2024-10-17T17:59:10.354Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-21655 vulnerable 2026-06-03 14:54:50.422316 Insufficient control of custom field value sizes
MEDIUM (4.3)
Discourse is a platform for community discussion. For fields that are client editable, limits on sizes are not imposed. This allows a malicious actor to cause a Discourse instance to use excessive disk space and also often excessive bandwidth. The issue is patched 3.1.4 and 3.2.0.beta4.
Published: 2024-01-12T20:46:00.196Z
Updated: 2025-06-03T14:03:56.412Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-49099 vulnerable 2026-06-03 14:53:20.153036 Discourse secure uploads accessible to guests even when login is required
LOW (3.1)
Discourse is a platform for community discussion. Under very specific circumstances, secure upload URLs associated with posts can be accessed by guest users even when login is required. This vulnerability has been patched in 3.2.0.beta4 and 3.1.4.
Published: 2024-01-12T20:53:53.163Z
Updated: 2025-06-17T21:09:17.903Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-48297 vulnerable 2026-06-03 14:53:18.886671 Discourse vulnerable to unlimited mentioned users in message serializer
HIGH (8.6)
Discourse is a platform for community discussion. The message serializer uses the full list of expanded chat mentions (@all and @here) which can lead to a very long array of users. This issue was patched in versions 3.1.4 and beta 3.2.0.beta5.
Published: 2024-01-12T20:35:02.394Z
Updated: 2025-06-17T21:09:17.756Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-47121 vulnerable 2026-06-03 14:53:16.891983 Discourse SSRF vulnerability in Embedding
LOW (3.4)
Discourse is an open source platform for community discussion. Prior to version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, the embedding feature is susceptible to server side request forgery. The issue is patched in version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches. As a workaround, disable the Embedding feature.
Published: 2023-11-10T15:13:42.254Z
Updated: 2025-02-27T20:33:47.097Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-47120 vulnerable 2026-06-03 14:53:16.891420 Discourse DoS through Onebox favicon URL
HIGH (7.5)
Discourse is an open source platform for community discussion. In versions 3.1.0 through 3.1.2 of the `stable` branch and versions 3.1.0,beta6 through 3.2.0.beta2 of the `beta` and `tests-passed` branches, Redis memory can be depleted by crafting a site with an abnormally long favicon URL and drafting multiple posts which Onebox it. The issue is patched in version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches. There are no known workarounds.
Published: 2023-11-10T15:09:54.389Z
Updated: 2024-09-03T18:55:29.162Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-47119 vulnerable 2026-06-03 14:53:16.888563 HTML injection in oneboxed links
MEDIUM (5.3)
Discourse is an open source platform for community discussion. Prior to version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, some links can inject arbitrary HTML tags when rendered through our Onebox engine. The issue is patched in version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches. There are no known workarounds.
Published: 2023-11-10T15:00:38.158Z
Updated: 2024-09-03T18:56:52.373Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-46130 vulnerable 2026-06-03 14:53:08.996376 Bypassing height value allowed in some theme components
MEDIUM (4.3)
Discourse is an open source platform for community discussion. Prior to version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, some theme components allow users to add svgs with unlimited `height` attributes, and this can affect the availability of subsequent replies in a topic. Most Discourse instances are unaffected, only instances with the svgbob or the mermaid theme component are within scope. The issue is patched in version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches. As a workaround, disable or remove the relevant theme components.
Published: 2023-11-10T14:54:48.828Z
Updated: 2024-09-03T18:57:10.938Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-45816 vulnerable 2026-06-03 14:53:08.643932 Unread bookmark reminder notifications that the user cannot access can be seen
LOW (3.3)
Discourse is an open source platform for community discussion. Prior to version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, there is an edge case where a bookmark reminder is sent and an unread notification is generated, but the underlying bookmarkable (e.g. post, topic, chat message) security has changed, making it so the user can no longer access the underlying resource. As of version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, bookmark reminders are now no longer sent if the user does not have access to the underlying bookmarkable, and also the unread bookmark notifications are always filtered by access. There are no known workarounds.
Published: 2023-11-10T14:49:27.544Z
Updated: 2024-09-03T17:43:21.614Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-45806 vulnerable 2026-06-03 14:53:08.620859 Discourse vulnerable to DoS via Regexp Injection in Full Name
MEDIUM (4.3)
Discourse is an open source platform for community discussion. Prior to version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches, if a user has been quoted and uses a `|` in their full name, they might be able to trigger a bug that generates a lot of duplicate content in all the posts they've been quoted by updating their full name again. Version 3.1.3 of the `stable` branch and version 3.2.0.beta3 of the `beta` and `tests-passed` branches contain a patch for this issue. No known workaround exists, although one can stop the "bleeding" by ensuring users only use alphanumeric characters in their full name field.
Published: 2023-11-10T14:43:37.657Z
Updated: 2024-09-03T17:43:41.680Z
Reference links
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.