Drupal Core: Ajax Status Messages Can Run Injected Scripts

Published as "Drupal Core Cross-Site Scripting (XSS)"

medium Drupal · Last reviewed Nov 9, 2026

CVE: CVE-2024-12393
GHSA: GHSA-8mvq-8h2v-j9vf
Packagist: PKSA-yjvc-rnsz-8n3c
Reported: Dec 10, 2024

Lets a logged-in user get script into status messages that Drupal renders with JavaScript, in some site configurations.

Affected and fixed versions

In 2 packages: drupal/core and drupal/core-recommended. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
11.0.0 – 11.0.7	11.0.8
10.3.0 – 10.3.8	10.3.9
8.8.0 – 10.2.10	10.2.11

Upgrade

Run the line for the branch you are on. 1 other package listed above is affected too; update it the same way.

composer require drupal/core:^11.0.8
composer require drupal/core:^10.3.9
composer require drupal/core:^10.2.11

What this means

Some Drupal status messages could carry script that runs in another user's browser. This is cross-site scripting (XSS): an attacker gets their own JavaScript to run on your site, inside someone else's session. Drupal renders some status messages with JavaScript, and in certain situations it didn't clean them first.

Who is affected

Sites on drupal/core 8.8.0 and later below 10.2.11, 10.3.0 below 10.3.9, and 11.0.0 below 11.0.8. Drupal rates the attack as needing an ordinary user account, and says it applies only in some cases and configurations.

The fix is in Drupal\Core\Ajax\MessageCommand, which now filters plain-string messages before sending them to the browser. Ajax callbacks in custom or contributed modules that build a MessageCommand from text a user can influence are the place to check. Drupal 7 is not affected.

What to do

Update to the fixed release for your branch: 10.2.11, 10.3.9 or 11.0.8. Drupal 8, Drupal 9 and Drupal 10 before 10.2 no longer get security fixes. See SA-CORE-2024-003.

Reported by Jay Beaton.

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 Core: Ajax Status Messages Can Run Injected Scripts (CVE-2024-12393, GHSA-8mvq-8h2v-j9vf)
Details: https://phpnews.net/security/drupal/ghsa-8mvq-8h2v-j9vf

Affected versions, as Composer constraints:
- drupal/core, drupal/core-recommended: >=11.0.0,<11.0.8|>=10.3.0,<10.3.9|>=8.8.0,<10.2.11

Fixed releases:
- 11.0.0 – 11.0.7: update to 11.0.8
- 10.3.0 – 10.3.8: update to 10.3.9
- 8.8.0 – 10.2.10: update to 10.2.11

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-8mvq-8h2v-j9vf 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