How severe is CVE-2017-6926?

CVE-2017-6926 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-6926?

CVE-2017-6926 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-6926?

Update drupal/core to 8.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-6926 is resolved across your whole dependency graph.

How do I detect CVE-2017-6926 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-6926 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2017-6926 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-6926 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-6926?

CVE-2017-6926 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-6926?

CVE-2017-6926 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-6926 published, and has it been updated?

CVE-2017-6926 was published on March 1, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2017-6926 — core

HIGH

CVE-2017-6926 is a high-severity (CVSS 8.1) Information Exposure vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Drupal Comment reply form allows access to restricted content

Also known asGHSA-2p28-5mvp-2j2r

Published

Mar 1, 2018

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/drupal🐘drupal/drupal

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.4.0&&< 8.4.5	8.4.5`composer require drupal/core:^8.4.5`
🐘Packagist	`drupal/core`	≥ 7.0&&< 7.57	7.57`composer require drupal/core:^7.57`
🐘Packagist	`drupal/drupal`	≥ 8.4.0&&< 8.4.5	8.4.5`composer require drupal/drupal:^8.4.5`
🐘Packagist	`drupal/drupal`	≥ 7.0&&< 7.57	7.57`composer require drupal/drupal:^7.57`

Affected Products

1 product · 1 configurations

Application

drupaldrupal

≥ 8.4.0 && < 8.4.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 8.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-6926 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-6926 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

security-advisories

4.8/10

Code-Review10/10

Maintained10/10

Branch-Protection0/10

Assessed Nov 9, 2026

Timeline

Disclosed

Mar 1, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2017-6926

GHSA-2p28-5mvp-2j2r

References

Advisorydrupal.org · sa core 2018 001 Advisorynvd.nist.gov · CVE 2017 6926 Webgithub.com · CVE 2017 6926.yaml Webgithub.com · CVE 2017 6926.yaml Packagegithub.com · core

Related vulnerabilities

This CVE is high severity; 1 of 8 other CVEs affecting drupal/core is rated as high or higher (top: critical).

CVE-2026-6365CVE-2026-9082CVE-2026-6367CVE-2026-6366CVE-2025-13080CVE-2025-13082CVE-2025-13081CVE-2025-13083

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026