DrupalCMS
CVE-2017-6925
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 · uneditedIn versions of Drupal 8 core prior to 8.3.7; There is a vulnerability in the entity access system that could allow unwanted access to view, create, update, or delete entities. This only affects entities that do not use or do not have UUIDs, and entities that have different access restrictions on different revisions of the same entity.
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 confidenceDrupal 8 core versions prior to 8.3.7 contain a flaw in the entity access system where entities without UUIDs or entities with different access restrictions across revisions can be accessed without proper authorization, allowing unauthorized view, create, update, or delete operations.
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
>= 8.0.0, < 8.3.7CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Drupal 8 core versionRun 'drush status' or check the CHANGELOG.txt file in the Drupal root directory for the version numberAffected if The installed version is 8.0.0 or higher but lower than 8.3.7
-
Identify entities without UUIDsQuery the database: SELECT id, entity_type, uuid FROM {entity} WHERE uuid IS NULL or query your specific entity tables to find records with NULL uuid valuesAffected if Any entities exist in the system that lack a UUID value
-
Check for revisioned entities with access variationsReview content types with revisions enabled and examine whether access restrictions differ between revisions of the same entity. Query revision tables (e.g., node_revision) and compare access-related fields across revisions for the same entity IDAffected if Content types with revisions are enabled and different revisions of the same entity have varying access control settings
The environment is affected if Drupal 8 core version is 8.0.0 through 8.3.6 AND the site uses entities without UUIDs or entities with revision history where access restrictions vary between revisions.
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.
dbcve · scoped8.3.7
Upgrade Drupal 8 core to version 8.3.7 or later to patch the entity access bypass vulnerability.
Drupal 8.3.7 or later (latest 8.x stable)
- 1. Back up the entire Drupal site database and files before any update
- 2. Update Drupal core to version 8.3.7 or later (recommended: latest stable 8.x release)
- 3. Run database updates using 'drush updatedb' or via the web interface at /update.php
- 4. Clear all Drupal caches using 'drush cr' or through the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6925 — 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-2017-6925 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