dbcve.org
DrupalCMS

CVE-2017-6931

MEDIUM · 6.5 CVSS v3.0 Published 2018-03-01
Fix available
A fix is available. Upgrade to 8.4.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 the Settings Tray module has a vulnerability that allows users to update certain data that they do not have the permissions for. If you have implemented a Settings Tray form in contrib or a custom module, the correct access checks should be added. This release fixes the only two implementations in core, but does not harden against other such bypasses. This vulnerability can be mitigated by disabling the Settings Tray module.

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

The Settings Tray module in Drupal 8.4.x before 8.4.5 contains an access control bypass that allows authenticated users to update certain data they lack permissions for. Forms implemented through the Settings Tray API do not properly enforce permission checks, enabling privilege escalation.

MitigationUpdate to Drupal 8.4.5 or later to patch the core implementations, and for any custom or contrib modules using Settings Tray forms, manually add proper access checks using the correct access callback mechanisms.

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Determine Drupal core version
    Run `drush status --fields=drupal-version` or inspect the VERSION constant in core/lib/Drupal.php or the version entry in composer.json.
    Affected if Installed version is >= 8.4.0 and < 8.4.5 (specifically 8.4.0, 8.4.1, 8.4.2, 8.4.3, or 8.4.4)
  2. Check if Settings Tray module is enabled
    Run `drush pm-list --status=enabled --type=module` and look for 'settings_tray' in the output, or query the database: SELECT status FROM system WHERE name = 'settings_tray' AND type = 'module';
    Affected if Settings Tray module is enabled and core version is in the affected 8.4.x range
  3. Identify custom or contrib modules using Settings Tray API
    Search the codebase for plugins annotated with 'settings_tray' form or services tagged with 'settings_tray.form' in *.yml files within modules/custom and modules/contrib directories.
    Affected if Custom or contrib modules implement Settings Tray forms and the core version is in the affected range
  4. Review user role permissions for Settings Tray-accessible entities
    Examine which authenticated roles have permissions to edit forms that may be exposed through Settings Tray (such as block, entity display settings, or other configuration forms). Use Drush: `drush role:list` and inspect role permissions.
    Affected if Authenticated users have elevated permissions on entity types exposed via Settings Tray in an affected version

You are affected if Drupal core version is 8.4.0 through 8.4.4 and the Settings Tray module is currently enabled.

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

Update to Drupal 8.4.5 or later to patch the core implementations, and for any custom or contrib modules using Settings Tray forms, manually add proper access checks using the correct access callback mechanisms.

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-6931 — 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-6931 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