Drupal sensitive information disclosure in Drupal/Core

drupal/core Updated 02 Oct 2025

Summary

17/05/2022
Yes i
Moderate
4.3

CVE-2016-9449: Drupal sensitive information disclosure. Affects drupal/core across 2 version ranges.

>= 7.0, < 7.52 >= 8.0, < 8.2.3

Fixed in 7.52 or 8.2.3, 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 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/Core is a popular open-source content management system (CMS) used for building websites and applications. It provides a flexible and extensible framework for managing and organizing content. The taxonomy module in Drupal/Core allows users to categorize and classify content using predefined terms. However, a vulnerability has been discovered in versions before 7.52 and 8.2.3 that could lead to sensitive information disclosure.

Vulnerability Detail

The vulnerability in the taxonomy module of Drupal/Core arises from inconsistent naming of access query tags. Remote authenticated users can exploit this vulnerability to obtain sensitive information about taxonomy terms. By leveraging the inconsistent naming, an attacker can bypass access controls and gain unauthorized access to sensitive data. This could potentially expose confidential information, compromise user privacy, and lead to further security breaches.

How To Fix

Fixed versions by release line

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

  • >= 7.0, < 7.52 7.52
    composer require drupal/core:7.52
  • >= 8.0, < 8.2.3 8.2.3
    composer require drupal/core:8.2.3

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 known workaround for this vulnerability. It is essential to apply the recommended fix by updating Drupal/Core to the patched version.

Conclusion

The vulnerability in the taxonomy module of Drupal/Core can allow remote authenticated users to obtain sensitive information. It is crucial to update Drupal/Core to the patched version to mitigate this vulnerability and prevent unauthorized access to confidential data. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for drupal/core →

Share this vulnerability

FAQ

Drupal/Core is an open-source content management system used for building websites and applications. It provides a flexible framework for managing and organizing content.

The taxonomy module in Drupal/Core allows users to categorize and classify content using predefined terms. It helps in organizing and structuring content.

The vulnerability in the taxonomy module allows remote authenticated users to obtain sensitive information about taxonomy terms by exploiting inconsistent naming of access query tags. This can lead to unauthorized access to confidential data.

The vulnerability could result in the exposure of sensitive information, compromise user privacy, and potentially lead to further security breaches. It is crucial to apply the recommended fix to mitigate these risks.

To fix this vulnerability, update Drupal/Core to version 7.52 or 8.2.3, depending on the installed version. This will ensure consistent naming of access query tags and prevent unauthorized access to sensitive information.

Related vulnerabilities

Recent vulnerabilities recorded for drupal/core.

How To Fix

Fixed versions by release line

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

  • >= 7.0, < 7.52 7.52
    composer require drupal/core:7.52
  • >= 8.0, < 8.2.3 8.2.3
    composer require drupal/core:8.2.3

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