Drupal Core: Error Pages Can Reveal the Site's Full Server Path

Published as "Drupal Full Path Disclosure"

medium Drupal · Last reviewed Nov 10, 2026

CVE: CVE-2024-45440
GHSA: GHSA-mg8j-w93w-xjgc
Packagist: PKSA-styk-3knc-d1bt
Reported: Aug 29, 2024

Can show anyone the full server path of a Drupal site when settings.php raises a PHP error on pages like core/authorize.php.

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.4	11.0.5
10.3.0 – 10.3.5	10.3.6
8.0.0 – 10.2.8	10.2.9

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.5
composer require drupal/core:^10.3.6
composer require drupal/core:^10.2.9

What this means

A visitor can learn the full path of your Drupal installation on the server. That isn't a break-in on its own, but it hands an attacker a detail that can help with other attacks.

Early pages such as core/authorize.php and core/install.php printed PHP errors raised while settings.php loaded, even with error messages set to display "None". See the Drupal issue and the fix.

Who is affected

Sites on drupal/core (or drupal/core-recommended) whose settings.php can raise a PHP warning or error. The reported case is $settings['hash_salt'] read with file_get_contents() from a file that is missing or empty, for example after the file was moved or deleted. Anyone can load these pages without logging in.

Sites whose settings.php loads without errors don't show the path. Only the path to the Drupal directory leaks, not files or data.

What to do

Update to 10.2.9, 10.3.6 or 11.0.5, depending on your branch.

Reported by SensCyberSecurity.

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: Error Pages Can Reveal the Site's Full Server Path (CVE-2024-45440, GHSA-mg8j-w93w-xjgc)
Details: https://phpnews.net/security/drupal/ghsa-mg8j-w93w-xjgc

Affected versions, as Composer constraints:
- drupal/core, drupal/core-recommended: >=8.0.0,<10.2.9|>=10.3.0,<10.3.6|>=11.0.0,<11.0.5

Fixed releases:
- 11.0.0 – 11.0.4: update to 11.0.5
- 10.3.0 – 10.3.5: update to 10.3.6
- 8.0.0 – 10.2.8: update to 10.2.9

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-mg8j-w93w-xjgc 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