CVE-2017-6379 json
Drupal Cross-Site Request Forgery (CSRF)
published 9y ago modified 4mo ago also GHSA-gxxq-fhc7-3jv9 , EUVD-2022-4035
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist drupal/core 8.2.7
- packagist drupal/drupal 8.2.7
Is CVE-2017-6379 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | drupal/core | >=8.2.0, <8.2.7 |
8.2.7 |
| packagist | drupal/drupal | >=8.2.0, <8.2.7 |
8.2.7 |
Affected products
- Drupal Drupal Core
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
securitytracker.com
/id/1038058
vdb-entry, web
-
drupal.org
/SA-2017-001
web, release-notes, third-party-advisory
-
securityfocus.com
/bid/96919
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2017-6379
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/drupal/core/CVE-2017-6379.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/drupal/drupal/CVE-2017-6379.yaml
web
-
github.com
/drupal/core
package
Sources
- CVE List CVE-2017-6379
- GitHub Advisory GHSA-gxxq-fhc7-3jv9
- NVD CVE-2017-6379
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.