DRUPAL-CORE-2023-005 in drupal/core
Published 19 Apr 2023 · Updated 19 Sept 2026
Affected package
- Affected
- >=8.0.0 <9.4.14 · >=9.5.0 <9.5.8 · >=10.0.0 <10.0.8
- Fixed in
- 9.4.14, 9.5.8, 10.0.8
composer require drupal/core:^10.0.8Details
The file download facility doesn't sufficiently sanitize file paths in certain situations. This may result in users gaining access to private files that they should not have access to.
Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing private files after updating.
This advisory is covered by [Drupal Steward](/steward). Because this vulnerability is not mass exploitable, your Steward partner may respond by monitoring-only, rather than enforcing a new WAF rule.
We would normally not apply for a release of this severity. However, in this case we have chosen to apply Drupal Steward security coverage to test our processes.
Drupal 7
- All Drupal 7 sites on Windows web servers are vulnerable.
- Drupal 7 sites on Linux web servers are vulnerable with certain file directory structures, or if a vulnerable contributed or custom file access module is installed.
Drupal 9 and 10
Drupal 9 and 10 sites are only vulnerable if certain contributed or custom file access modules are installed.
Is DRUPAL-CORE-2023-005 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.