How severe is CVE-2017-6379?

CVE-2017-6379 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-6379 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-6379?

CVE-2017-6379 primarily affects Drupal. In total, 12 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-6379?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-6379 published?

CVE-2017-6379 was published on 2017-03-16 and last updated on 2026-06-17.

CVE-2017-6379

CVE-2017-6379 is a high-severity vulnerability in Drupal with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.1
EPSS exploit prediction: 1% (51st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-352
Affected product: Drupal
Published: 2017-03-16
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2017-6379?: 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.
How severe is CVE-2017-6379?: CVE-2017-6379 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-6379 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-6379?: CVE-2017-6379 primarily affects Drupal. In total, 12 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-6379?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-6379 published?: CVE-2017-6379 was published on 2017-03-16 and last updated on 2026-06-17.

References

Affected products (12)

cpe:2.3:a:drupal:drupal:8.2.0:*:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.0:beta1:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.0:beta2:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.0:beta3:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.0:rc1:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.0:rc2:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.1:*:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.2:*:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.3:*:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.4:*:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.5:*:*:*:*:*:*:*
cpe:2.3:a:drupal:drupal:8.2.6:*:*:*:*:*:*:*

More vulnerabilities in Drupal

CVE-2009-3352 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in the quota_by_role (Quota by role) module for Drupal have unknown impact and…
CVE-2026-9082 — Critical (CVSS 9.8): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal Drupal…
CVE-2024-55638 — Critical (CVSS 9.8): Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core:…
CVE-2024-55637 — Critical (CVSS 9.8): Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core:…
CVE-2024-55636 — Critical (CVSS 9.8): Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core:…
CVE-2020-13675 — Critical (CVSS 9.8): Drupal's JSON:API and REST/File modules allow file uploads through their HTTP APIs. The modules do not correctly run…

All CVEs affecting Drupal →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →