CVE-2020-13663:
Drupal Core Cross-Site Request Forgery (CSRF) vulnerability
8.8
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.44691%
CWE
Published
5/24/2022
Updated
2/6/2024
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
drupal/core | composer | >= 8.9.0, < 8.9.1 | 8.9.1 |
drupal/core | composer | >= 9.0.0, < 9.0.1 | 9.0.1 |
drupal/core | composer | >= 7.0.0, < 7.72 | 7.72 |
drupal/core | composer | >= 8.0.0, < 8.8.8 | 8.8.8 |
drupal/drupal | composer | >= 7.0.0, < 7.72 | 7.72 |
drupal/drupal | composer | >= 8.0.0, < 8.8.8 | 8.8.8 |
drupal/drupal | composer | >= 8.9.0, < 8.9.1 | 8.9.1 |
drupal/drupal | composer | >= 9.0.0, < 9.0.1 | 9.0.1 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The primary vulnerability existed in FormBuilder::doBuildForm
, where the lack of input sanitization after detecting an invalid CSRF token allowed attackers to submit malicious payloads. The patch explicitly resets user input, POST data, and file uploads, confirming this was the root cause. The FormValidator::setInvalidTokenError
's message adjustment (removing the reload link) suggests a secondary mitigation, though its direct impact on the vulnerability is less critical. Test cases in the commit diff validate()
that form values were retained pre-patch, confirming the exploit path.