Drupal CKEditor 5: Some Image Uploads Can Move the Whole Webroot

Published as "Drupal core vulnerable to improper error handling"

medium Drupal · Last reviewed Nov 9, 2026

CVE: CVE-2024-11942
GHSA: GHSA-52jr-x6h6-xj6g
Packagist: PKSA-mh8z-kh9f-vv4z
Reported: Dec 5, 2024

Lets a malicious user take a Drupal 10 site offline through a CKEditor 5 image upload, on sites with several uncommon settings combined.

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.0.0 – 10.2.9	10.2.10

Upgrade

Run the line for the branch you are on.

composer require drupal/core:^10.2.10

What this means

On some Drupal 10 sites, a bug in the CKEditor 5 module could make an image upload move the entire webroot to a different place on the file system. A malicious user could use this to take the site down.

Who is affected

Sites on drupal/core 10.0.0 and later, below 10.2.10, that let users upload images through CKEditor 5. Drupal says several non-default site configurations must all be in place at once for this to happen, and its advisory does not list them. Drupal 10.3 and later are not affected, and neither is Drupal 7.

What to do

If you're on Drupal 10.2, update to 10.2.10. Drupal 10 releases before 10.2 no longer get security fixes, so sites on 10.0 or 10.1 should move to a supported release. See SA-CORE-2024-002.

Reported by Pierre Rudloff.

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 CKEditor 5: Some Image Uploads Can Move the Whole Webroot (CVE-2024-11942, GHSA-52jr-x6h6-xj6g)
Details: https://phpnews.net/security/drupal/ghsa-52jr-x6h6-xj6g

Affected versions, as Composer constraints:
- drupal/core: >=10.0.0,<10.2.10

Fixed releases:
- 10.0.0 – 10.2.9: update to 10.2.10

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-52jr-x6h6-xj6g 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