dbcve.org
DrupalCMS

CVE-2017-6930

HIGH · 8.1 CVSS v3.0 Published 2018-03-01
Fix available
A fix is available. Upgrade to 8.4.5 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Drupal versions 8.4.x versions before 8.4.5 when using node access controls with a multilingual site, Drupal marks the untranslated version of a node as the default fallback for access queries. This fallback is used for languages that do not yet have a translated version of the created node. This can result in an access bypass vulnerability. This issue is mitigated by the fact that it only applies to sites that a) use the Content Translation module; and b) use a node access module such as Domain Access which implement hook_node_access_records().

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 confidence

In Drupal 8.4.x before 8.4.5, when using node access controls on multilingual sites, Drupal incorrectly marks the untranslated version of a node as the default fallback for access queries in languages without translations. This allows bypass of access restrictions because the untranslated node's permissions are applied inappropriately to language variants that should have their own access controls.

MitigationUpgrade to Drupal 8.4.5 or later. Alternatively, if upgrading is not immediately feasible, disable either the Content Translation module or any node access modules (like Domain Access) that implement hook_node_access_records().

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
Affected:>= 8.4.0, < 8.4.5

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Drupal core version
    Run `drush status` or check the `core/lib/Drupal.php` file for the VERSION constant, or look at the `composer.json` file in the Drupal root
    Affected if The installed version is >= 8.4.0 and < 8.4.5
  2. Verify multilingual configuration
    Navigate to Configuration > Languages (/admin/config/regional/language) or run `drush config-get system.site` to check if multiple languages are configured
    Affected if More than one language is enabled on the site (including the default language plus additional languages)
  3. Confirm Content Translation module is enabled
    Run `drush pm-list --status=enabled --type=module` and look for 'translation' module, or check /admin/modules for the Content Translation module
    Affected if The Content Translation module is enabled and providing translations for content nodes
  4. Check for node access modules
    Review enabled modules for any that implement hook_node_access_records() - common examples include Domain Access, Workbench Access, or custom node access modules. Run `drush hook_node_access_records` if available or inspect module code
    Affected if Any node access control module that implements hook_node_access_records() is enabled on a multilingual site

The site is affected if running Drupal 8.4.0-8.4.4 with multilingual configuration AND either Content Translation or another node access module enabled, allowing untranslated node permissions to incorrectly apply to language variants.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 8.4.5 or later
Fixed in 8.4.5
Interim mitigation

Upgrade to Drupal 8.4.5 or later. Alternatively, if upgrading is not immediately feasible, disable either the Content Translation module or any node access modules (like Domain Access) that implement hook_node_access_records().

Fix this in Drupal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6930 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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