DRUPAL-CORE-2020-004 BIT-drupal-2020-13663 CVE-2020-13663 GHSA-m648-hpf8-qcjw

Drupal Core Cross-Site Request Forgery (CSRF) vulnerability

High Packagist

Severity: 8.8 / 10; High · CVSS 3.1
Exploit chance (EPSS): 0.69%; Chance of exploitation in the next 30 days. Higher than 53.01% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-352 Cross-Site Request Forgery (CSRF)
Fix: Available; 2 packages have a fixed version

Description

The Drupal core Form API does not properly handle certain form input from cross-site requests, which can lead to other vulnerabilities.

Affected versions

Packagist

Package	Vulnerable	Fixed in
drupal/core	`>= 8.0.0, < 8.8.8` `>= 8.9.0, < 8.9.1` `>= 9.0.0, < 9.0.1`	`8.8.8` `8.9.1` `9.0.1`
drupal/core	`>= 8.9.0, < 8.9.1`	`8.9.1`
drupal/core	`>= 9.0.0, < 9.0.1`	`9.0.1`
drupal/core	`>= 7.0.0, < 7.72`	`7.72`
drupal/core	`>= 8.0.0, < 8.8.8`	`8.8.8`
drupal/drupal	`>= 7.0.0, < 7.72`	`7.72`
drupal/drupal	`>= 8.0.0, < 8.8.8`	`8.8.8`
drupal/drupal	`>= 8.9.0, < 8.9.1`	`8.9.1`
drupal/drupal	`>= 9.0.0, < 9.0.1`	`9.0.1`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

drupal/core Packagist → `9.0.1`

composer

composer require drupal/core:^9.0.1

drupal/drupal Packagist → `7.72`

composer

composer require drupal/drupal:^7.72

Severity breakdown

CVSS 3.1 8.8

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

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Weakness

CWE-352: Cross-Site Request Forgery (CSRF)

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

How to prevent it

Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
Architecture and Design: Do not use the GET method for any request that triggers a state change.
Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2020-13663

Packages

github.com/drupal/core

Timeline

Jun 17, 2020 Published
Sep 19, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
DRUPAL-CORE-2026-004 Drupal Core has a SQL Injection issue	Critical Known exploited	Also affects drupal/core
CVE-2020-28949 Multiple vulnerabilities through filename manipulation in Archive_Tar	High Known exploited	Also affects drupal/core
CVE-2020-13671 Drupal core Unrestricted Upload of File with Dangerous Type	High Known exploited	Also affects drupal/core
CVE-2019-6340 Drupal Core Remote Code Execution Vulnerability	High Known exploited	Also affects drupal/core
CVE-2018-7602 Drupal Core Remote Code Execution Vulnerability	Critical Known exploited	Also affects drupal/core
CVE-2018-7600 Drupal Core Remote Code Execution Vulnerability	Critical Known exploited	Also affects drupal/core
DRUPAL-CORE-2026-016 The Navigation module doesn't sufficiently sanitize certain attributes, which can lead to a cross-site scripting (XSS) vulnerability.	Not rated yet	Also affects drupal/core
DRUPAL-CORE-2026-015 The Drupal core Link module provides a field type that can be used for internal and external URLs.	Not rated yet	Also affects drupal/core

Credits: Dor Tumarkin, Samuel Mortenson

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor