# CVE-2024-45440: Drupal Full Path Disclosure > Attackers can obtain full path disclosure in Drupal core when a specific file is missing, potentially aiding further attacks. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Aug 2024 - **Updated:** 21 Apr 2025 - **Also known as:** CLSA-2026-1793202127, GHSA-mg8j-w93w-xjgc, UBUNTU-CVE-2024-45440 ## What is CVE-2024-45440? CVE-2024-45440 is a medium-severity vulnerability in Drupal Drupal, published on 29 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description core/authorize.php in Drupal 11.x-dev allows Full Path Disclosure (even when error logging is None) if the value of hash_salt is file_get_contents of a file that does not exist. Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information) ## Which versions are affected by CVE-2024-45440? 18 open source packages ship an affected version, including drupal/core, drupal/core-recommended and drupal/drupal. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `drupal/core` | Packagist | From 10.3.0 | 10.3.6 | | `drupal/core` | Packagist | From 10.3.0 | 10.3.6 | | `drupal/core` | Packagist | From 11.0.0 | 11.0.5 | | `drupal/core` | Packagist | From 11.0.0 | 11.0.5 | | `drupal/core` | Packagist | From 8.0.0 | 10.2.9 | | `drupal/core` | Packagist | From 8.0.0 | 10.2.9 | | `drupal/core-recommended` | Packagist | From 10.3.0 | 10.3.6 | | `drupal/core-recommended` | Packagist | From 10.3.0 | 10.3.6 | | `drupal/core-recommended` | Packagist | From 11.0.0 | 11.0.5 | | `drupal/core-recommended` | Packagist | From 11.0.0 | 11.0.5 | | `drupal/core-recommended` | Packagist | From 8.0.0 | 10.2.9 | | `drupal/core-recommended` | Packagist | From 8.0.0 | 10.2.9 | | `drupal/drupal` | Packagist | From 10.3.0 | 10.3.6 | | `drupal/drupal` | Packagist | From 10.3.0 | 10.3.6 | | `drupal/drupal` | Packagist | From 11.0.0 | 11.0.5 | | `drupal/drupal` | Packagist | From 11.0.0 | 11.0.5 | | `drupal/drupal` | Packagist | From 8.0.0 | 10.2.9 | | `drupal/drupal` | Packagist | From 8.0.0 | 10.2.9 | Products: Drupal Drupal. ## How do I fix CVE-2024-45440? Upgrade drupal/core to a fixed version for your release line: 10.3.6, 11.0.5 or 10.2.9. ## Is CVE-2024-45440 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45440 exists. Public exploit code: - Drupal CVE-2024-45440 (github_poc): https://github.com/w0r1i0g1ht/CVE-2024-45440 - Enumeration tool for CVE-2024-45440 (github_poc): https://github.com/zoomdbz/CVE-2024-45440 - Drupal 11.x-dev - Full Path Disclosure (exploitdb) - Drupal 11.x-dev - Full Path Disclosure (nuclei): http/cves/2024/CVE-2024-45440.yaml ## Other vulnerabilities in Drupal Drupal - [CVE-2026-9082](https://insights.sbomify.com/CVE-2026-9082/): Drupal Core SQL Injection (critical 9.8, exploited in the wild) - [CVE-2020-13671](https://insights.sbomify.com/CVE-2020-13671/): Drupal core Un-restricted Upload of File (high 8.8, exploited in the wild) - [CVE-2019-6340](https://insights.sbomify.com/CVE-2019-6340/): Drupal Core Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2009-3352](https://insights.sbomify.com/CVE-2009-3352/): Other in n/a (critical 10.0) - [CVE-2024-55636](https://insights.sbomify.com/CVE-2024-55636/): Drupal core - Less critical - Gadget chain - SA-CORE-2024-006 (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-45440 and fix it if it is affected. What it is: CVE-2024-45440 is a medium-severity vulnerability in Drupal Drupal, published on 29 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45440 exists. Affected packages and fixed versions: - drupal/core (Packagist): affected from 10.3.0; fixed in 10.3.6 - drupal/core (Packagist): affected from 10.3.0; fixed in 10.3.6 - drupal/core (Packagist): affected from 11.0.0; fixed in 11.0.5 - drupal/core (Packagist): affected from 11.0.0; fixed in 11.0.5 - drupal/core (Packagist): affected from 8.0.0; fixed in 10.2.9 - drupal/core (Packagist): affected from 8.0.0; fixed in 10.2.9 - drupal/core-recommended (Packagist): affected from 10.3.0; fixed in 10.3.6 - drupal/core-recommended (Packagist): affected from 10.3.0; fixed in 10.3.6 - drupal/core-recommended (Packagist): affected from 11.0.0; fixed in 11.0.5 - drupal/core-recommended (Packagist): affected from 11.0.0; fixed in 11.0.5 - drupal/core-recommended (Packagist): affected from 8.0.0; fixed in 10.2.9 - drupal/core-recommended (Packagist): affected from 8.0.0; fixed in 10.2.9 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-45440/ (Markdown: https://insights.sbomify.com/CVE-2024-45440/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45440 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45440 - OSV: https://osv.dev/vulnerability/CVE-2024-45440 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-45440/ Summaries are generated and may contain mistakes; the official description above is the record.