Drupal core Denial of Service in drupal/drupal

drupal/drupal Updated 02 Oct 2025

Summary

15/05/2024
MODERATE
Yes i
Moderate
5.3

GHSA-w333-5f96-mjrr: Drupal core Denial of Service. Affects drupal/drupal across 2 version ranges.

>= 8.0.0, < 8.7.11 >= 8.8.0, < 8.8.1

Fixed in 8.7.11 or 8.8.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Drupal is a popular open-source content management system (CMS) written in PHP. It provides a flexible platform for building websites and applications. The vulnerability in the Drupal core affects versions 8.0.0 to 8.7.11 and 8.8.0 to 8.8.1. This vulnerability can lead to a Denial of Service (DoS) attack, where a visit to install.php can corrupt cached data, impairing the site until caches are rebuilt.

Vulnerability Detail

The vulnerability in Drupal core arises from a flaw in the handling of cached data during the installation process. When a user visits install.php, it triggers a corruption of cached data, which can cause the site to become impaired until the caches are rebuilt. This vulnerability can be exploited by an attacker to disrupt the normal functioning of a Drupal site, potentially leading to service unavailability and loss of data. The severity of this vulnerability is rated as MODERATE with a CVSS score of 5.3.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 8.0.0, < 8.7.11 8.7.11
    composer require drupal/drupal:8.7.11
  • >= 8.8.0, < 8.8.1 8.8.1
    composer require drupal/drupal:8.8.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. The recommended solution is to apply the available patches or upgrade to the fixed versions as mentioned in the 'how_to_fix' section.

Conclusion

The Drupal core Denial of Service vulnerability can lead to a disruption of normal site functioning and potential loss of data. It is crucial for Drupal site administrators to apply the necessary patches or upgrade to the fixed versions to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for drupal/drupal →

Share this vulnerability

FAQ

Drupal is an open-source content management system (CMS) written in PHP. It provides a flexible platform for building websites and applications.

A Denial of Service (DoS) attack is a malicious attempt to disrupt the normal functioning of a network, system, or application, making it unavailable to its intended users.

This vulnerability can be exploited by visiting the install.php page of a vulnerable Drupal site, causing cached data corruption and impairing the site until caches are rebuilt.

The potential consequences of this vulnerability include service unavailability, loss of data, and disruption of normal site functionality.

To fix this vulnerability, Drupal site administrators should update their installations to the fixed versions mentioned in the 'how_to_fix' section.

Related vulnerabilities

Recent vulnerabilities recorded for drupal/drupal.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 8.0.0, < 8.7.11 8.7.11
    composer require drupal/drupal:8.7.11
  • >= 8.8.0, < 8.8.1 8.8.1
    composer require drupal/drupal:8.8.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback