Drupal Comment Module: Crafted Reply Requests Can Take a Site Down

Published as "Drupal core Denial of Service"

high Drupal · Last reviewed Nov 9, 2026

CVE: CVE-2024-11941
GHSA: GHSA-xq54-x54m-vcpx
Packagist: PKSA-q8r5-cgs2-dxxk
Reported: Dec 5, 2024

Lets an attacker cause a denial of service with comment reply requests on Drupal sites that use the core Comment module.

Affected and fixed versions

In drupal/core. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
10.2.0 – 10.2.1	10.2.2
10.1.0 – 10.1.7	10.1.8

Upgrade

Run the line for the branch you are on.

composer require drupal/core:^10.2.2
composer require drupal/core:^10.1.8

What this means

An attacker could send comment reply requests that trigger a denial of service (DoS), where the site stops answering normal visitors. Drupal's risk rating says the attacker doesn't need to log in.

Who is affected

Drupal sites that use the core Comment module and haven't updated to 10.1.8 or 10.2.2. Drupal says this happens only in certain cases, without listing them. Sites that don't use the Comment module are not affected, and neither is Drupal 7.

What to do

Update to 10.2.2 if you're on Drupal 10.2, or 10.1.8 if you're on Drupal 10.1. Drupal 8, Drupal 9 and Drupal 10 before 10.1 no longer get security fixes. See SA-CORE-2024-001.

Reported by Alexander Antonenko and Doug Green.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Drupal Comment Module: Crafted Reply Requests Can Take a Site Down (CVE-2024-11941, GHSA-xq54-x54m-vcpx)
Details: https://phpnews.net/security/drupal/ghsa-xq54-x54m-vcpx

Affected versions, as Composer constraints:
- drupal/core: >=10.2.0,<10.2.2|>=10.1.0,<10.1.8

Fixed releases:
- 10.2.0 – 10.2.1: update to 10.2.2
- 10.1.0 – 10.1.7: update to 10.1.8

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/drupal/ghsa-xq54-x54m-vcpx and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Drupal advisories