Drupal Incorrect cache context on password reset page

drupal/core Updated 02 Oct 2025

Summary

17/05/2022
Yes i
High
7.5

CVE-2016-9450: Drupal Incorrect cache context on password reset page. Affects drupal/core versions >= 8.0, < 8.2.3. Fixed in 8.2.3. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 question affects Drupal versions 8.x before 8.2.3. Drupal's user password reset form is susceptible to cache poisoning attacks due to an incorrect cache context. This vulnerability can be exploited remotely by attackers.

Vulnerability Detail

The user password reset form in Drupal 8.x before 8.2.3 does not specify the correct cache context. This allows remote attackers to conduct cache poisoning attacks. By exploiting this vulnerability, an attacker can manipulate the cache and potentially gain unauthorized access or perform other malicious activities. The vulnerability has a CVSS score of 7.5, indicating a high severity level.

How To Fix

Minimum fixed version

8.2.3

This is the first release that contains the fix.

composer require drupal/core:8.2.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. The recommended solution is to upgrade to the fixed version of Drupal.

Conclusion

The vulnerability in Drupal's user password reset form can be exploited by remote attackers to conduct cache poisoning attacks. To mitigate this vulnerability, it is crucial to upgrade to Drupal version 8.2.3 or later. This will ensure the correct cache context is specified on the password reset page, preventing potential unauthorized access or malicious activities. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for drupal/core →

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 cache poisoning attack is a type of attack where an attacker manipulates the cache to serve malicious content or gain unauthorized access.

This vulnerability allows remote attackers to conduct cache poisoning attacks, potentially leading to unauthorized access or other malicious activities.

To fix this vulnerability, upgrade to Drupal version 8.2.3 or later.

No specific workaround is available. Upgrading to the fixed version is recommended.

Related vulnerabilities

Recent vulnerabilities recorded for drupal/core.

How To Fix

Minimum fixed version

8.2.3

This is the first release that contains the fix.

composer require drupal/core:8.2.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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