NVD / CVE Program· CNA GitHub_M

CVE-2024-37299: Discourse vulnerable to DoS via Tag Group

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: discourse discourse 3.2.5.
Severity is disputed: the assigning authority (CNA) scores it 4.9, NVD 7.5.

Low priority for now. Upgrade to discourse discourse 3.2.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Discourse is an open source discussion platform. Prior to 3.2.5 and 3.3.0.beta5, crafting requests to submit very long tag group names can reduce the availability of a Discourse instance. This vulnerability is fixed in 3.2.5 and 3.3.0.beta5.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jul 30, 2024
Updated: Jun 17, 2026
EPSS: 0.5% · 48th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · GitHub_M: 4.9; 2.6 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
discourse	discourse	cpe:2.3:a:discourse:discourse

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

discourse discoursebefore 3.2.5
discourse discourse3.3.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

discourse discourse
- < 3.2.5, >= 3.3.0.beta1, < 3.3.0.beta5affected

Same product

discourse: all records

Other highest-scoring records for the same primary product.

CVE-2021-41163RCE via malicious SNS subscription payload
45Plan
CVE-2025-68662FinalDestination hostname matching allows SSRF protection bypass
39Monitor
CVE-2023-47121Discourse SSRF vulnerability in Embedding
39Monitor

Published before and after this one in the same product

← EarlierCVE-2024-38360Jul 15, 2024 · Denial of service via Watched Words in Discourse
19Monitor
← EarlierCVE-2024-37165Jul 30, 2024 · Discourse has an XSS via Onebox system
24Monitor
Later →CVE-2024-39320Jul 30, 2024 · Discourse allows iframe injection though default site setting
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
discourse discourse	3.2.5 · description	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-48053314 days apartDiscourse vulnerable to DoS via large URL payload in PM to a bot
34Monitor
CVE-2024-24827137 days apartNo rate limits on POST /uploads endpoint in Discourse
30Monitor
CVE-2023-48297200 days apartDiscourse vulnerable to unlimited mentioned users in message serializer
30Monitor
CVE-2023-44388288 days apartMalicious requests can fill up the log files resulting in a deinal of service in Discourse
30Monitor
CVE-2023-36818382 days apartDenial of service via User Custom Sidebar Section Unlimited Link Creation in discourse
30Monitor
CVE-2024-27100137 days apartDenial of service via Staff Actions in Discourse
26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

Fix✗ → ✓Sep 29, 2026, 11:48 AM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/discourse/discourse/commit/188cb58daa833839c54c266ce22db150a3f3a210

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records