7.5
CWE
345
Advisory Published
CVE Published
Updated

CVE-2016-9450

First published: Wed Nov 16 2016(Updated: )

Incorrect cache context on password reset page

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
composer/drupal/core>=8.0<8.1.0>=8.1.0<8.2.0>=8.2.0<8.2.3
composer/drupal/drupal>=8.0<8.1.0>=8.1.0<8.2.0>=8.2.0<8.2.3
composer/drupal/drupal>=8.0<8.2.3
8.2.3
composer/drupal/core>=8.0<8.2.3
8.2.3
Drupal=8.0.0
Drupal=8.0.0-alpha10
Drupal=8.0.0-alpha11
Drupal=8.0.0-alpha12
Drupal=8.0.0-alpha13
Drupal=8.0.0-alpha14
Drupal=8.0.0-alpha15
Drupal=8.0.0-alpha2
Drupal=8.0.0-alpha3
Drupal=8.0.0-alpha4
Drupal=8.0.0-alpha5
Drupal=8.0.0-alpha6
Drupal=8.0.0-alpha7
Drupal=8.0.0-alpha8
Drupal=8.0.0-alpha9
Drupal=8.0.0-beta1
Drupal=8.0.0-beta10
Drupal=8.0.0-beta11
Drupal=8.0.0-beta12
Drupal=8.0.0-beta13
Drupal=8.0.0-beta14
Drupal=8.0.0-beta15
Drupal=8.0.0-beta16
Drupal=8.0.0-beta2
Drupal=8.0.0-beta3
Drupal=8.0.0-beta4
Drupal=8.0.0-beta6
Drupal=8.0.0-beta7
Drupal=8.0.0-beta9
Drupal=8.0.0-rc1
Drupal=8.0.0-rc2
Drupal=8.0.0-rc3
Drupal=8.0.0-rc4
Drupal=8.0.1
Drupal=8.0.2
Drupal=8.0.3
Drupal=8.0.4
Drupal=8.0.5
Drupal=8.0.6
Drupal=8.1.0
Drupal=8.1.0-beta1
Drupal=8.1.0-beta2
Drupal=8.1.0-rc1
Drupal=8.1.1
Drupal=8.1.2
Drupal=8.1.3
Drupal=8.1.4
Drupal=8.1.5
Drupal=8.1.6
Drupal=8.1.7
Drupal=8.1.8
Drupal=8.1.9
Drupal=8.1.10
Drupal=8.2.0
Drupal=8.2.0-beta1
Drupal=8.2.0-beta2
Drupal=8.2.0-beta3
Drupal=8.2.0-rc1
Drupal=8.2.0-rc2
Drupal=8.2.1
Drupal=8.2.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2016-9450?

    CVE-2016-9450 is rated as a moderate severity vulnerability due to its potential for cache poisoning attacks.

  • How do I fix CVE-2016-9450?

    To fix CVE-2016-9450, update your Drupal installation to version 8.2.3 or later.

  • What versions of Drupal are affected by CVE-2016-9450?

    CVE-2016-9450 affects Drupal versions 8.0.0 through 8.2.2.

  • What is the impact of exploiting CVE-2016-9450?

    Exploitation of CVE-2016-9450 may allow an attacker to perform cache poisoning, potentially affecting the integrity of cached content.

  • Is there a workaround for CVE-2016-9450?

    There is no official workaround for CVE-2016-9450; the recommended action is to update to the secured version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203