CVE-2017-6926

In Drupal versions 8.4.x versions before 8.4.5 users with permission to post comments are able to view content and comments they do not have access to, and are also able to add comments to this content. This vulnerability is mitigated by the fact that the comment system must be enabled and the attacker must have permission to post comments.

Published: 2018-03-01 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-6926 is rated Moderate Risk (56/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.23%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-6926

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.37% 1.23% +0.86%
2 2025-12-28 0.31% 0.37% +0.06%
3 2025-12-27 — 0.31% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-6926

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 5.2 [email protected]
5.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.0 4.9 [email protected]

Weakness enumeration for CVE-2017-6926

GitHub Security Advisory for CVE-2017-6926

GHSA-2p28-5mvp-2j2r · Severity: high · Ecosystem: composer — Drupal Comment reply form allows access to restricted content

Affected software / configurations for CVE-2017-6926

Vendor Product Version Raw CPE
drupal drupal >= 8.4.0, < 8.4.5 cpe:2.3:a:drupal:drupal:*:*:*:*:*:*:*:*

References for CVE-2017-6926

URL Tags
https://www.drupal.org/sa-core-2018-001 Vendor Advisory
cvelogic Threat Intelligence