Some administrative paths in Drupal 8.2.x before 8.2.7 did not include protection for CSRF. This would allow an attacker to disable some blocks on a site. This issue is mitigated by the fact that users would have to know the block ID.
Loading...
Loading...
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Some administrative paths in Drupal 8.2.x before 8.2.7 did not include protection for CSRF. This would allow an attacker to disable some blocks on a site. This issue is mitigated by the fact that users would have to know the block ID.
March 16, 2017
May 13, 2026
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| drupal/core | 8.2.0 ... 8.2.6 (7 versions) | 8.2.7 | — |
| drupal/drupal | 8.2.0 ... 8.2.6 (7 versions) | 8.2.7 | — |
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-6379
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.