DrupalCMS
CVE-2016-6212
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Views module 7.x-3.x before 7.x-3.14 in Drupal 7.x and the Views module in Drupal 8.x before 8.1.3 might allow remote authenticated users to bypass intended access restrictions and obtain sensitive Statistics information via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Views module in Drupal 7.x and 8.x contains an access control bypass vulnerability where authenticated users can access sensitive Statistics information that should be restricted. The vulnerability exists in the Views module versions prior to 7.x-3.14 (Drupal 7) and 8.1.3 (Drupal 8).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DrupalCMS
= 7.0= 7.1= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7= 7.8= 7.9= 7.10= 7.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Views module versionQuery the Drupal system table or use Drush command 'drush pm-list --status=enabled --type=module' to list enabled modules and their versions. Look for the Views module entry.Affected if The Views module version is below 7.x-3.14 for Drupal 7 or below 8.1.3 for Drupal 8.
-
Confirm the Drupal core versionCheck the Drupal core version by inspecting the 'VERSION' constant in includes/bootstrap.inc or running 'drush status' to see the Drupal version.Affected if The Drupal core is version 7.x or 8.x and the Views module version is vulnerable as determined in step 1.
-
Determine if the Statistics module is enabledCheck if the Statistics module is among enabled modules via Drush 'drush pm-list --status=enabled' or by examining the system table where modules are recorded as enabled.Affected if The Statistics module is enabled and the Views module version is vulnerable.
-
Inspect Statistics-related views for access control configurationAccess the Views UI at admin/structure/views and examine any views that display Statistics data (such as 'Popular content' or access logs). Check the 'Access' setting under the view's 'Advanced' section to see which roles can access these views.Affected if The view shows Statistics data is accessible to 'authenticated users' or roles that should not have access to sensitive statistics.
A user is affected if their Drupal installation runs Views module versions prior to 7.x-3.14 (Drupal 7) or 8.1.3 (Drupal 8), and the Statistics module is enabled with views accessible to roles that should be restricted from viewing sensitive statistics data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Drupal Views module to version 7.x-3.14 or later for Drupal 7.x, or 8.1.3 or later for Drupal 8.x. After upgrading, verify that the Statistics access controls are properly enforced.
Fix this in Drupal
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6212 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data