dbcve.org
DrupalCMS

CVE-2020-13663

HIGH · 8.8 CVSS v3.1 Published 2021-06-11
Fix available
A fix is available. Upgrade to 7.72 / 8.8.8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross Site Request Forgery vulnerability in Drupal Core Form API does not properly handle certain form input from cross-site requests, which can lead to other vulnerabilities.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Cross Site Request Forgery (CSRF) vulnerability in Drupal Core's Form API that fails to properly validate or reject form input originating from cross-site requests. The vulnerability allows attackers to potentially trick authenticated users into unknowingly submitting malicious form requests, which can lead to privilege escalation or execution of unintended actions.

MitigationApply the appropriate Drupal Core security patch or upgrade to a supported version that addresses this CSRF vulnerability, and ensure all custom forms utilize Drupal's built-in CSRF token validation mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DrupalCMS
Affected:>= 7.0, < 7.72>= 8.8.0, < 8.8.8>= 8.9.0, < 8.9.1>= 9.0.0, < 9.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Drupal Core version
    Locate the VERSION file in the Drupal root directory, or run 'drush status' and look for 'Drupal version', or check the 'version' field in composer.json
    Affected if The installed version falls within any of these ranges: >= 7.0 and < 7.72, >= 8.8.0 and < 8.8.8, >= 8.9.0 and < 8.9.1, or >= 9.0.0 and < 9.0.1
  2. Review custom form implementations for CSRF token usage
    Examine custom form builder functions in your modules (*.module files) and look for the presence of '#token' or 'form_token' in the form array definitions, or ensure forms are built using Drupal\Core\Form\FormBuilderInterface::getForm() which automatically includes tokens
    Affected if Custom forms do not include CSRF tokens (form_token) in their definition and are not built through the standard FormBuilder service
  3. Check for form validation hooks in custom modules
    Search module files for hook_form_alter or hook_form_BASE_FORM_ID_alter implementations and verify they do not remove or bypass the form_token element
    Affected if Form alter hooks are removing or disabling the form_token element that Drupal automatically adds to forms

You are affected if your Drupal Core version is below 7.72, below 8.8.8, below 8.9.1, or below 9.0.1, AND your custom forms do not implement proper CSRF token validation through Drupal's built-in mechanisms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.72 / 8.8.8 / 8.9.1 or later
Fixed in 7.728.8.88.9.1
Interim mitigation

Apply the appropriate Drupal Core security patch or upgrade to a supported version that addresses this CSRF vulnerability, and ensure all custom forms utilize Drupal's built-in CSRF token validation mechanisms.

Recommended fix High confidence

Drupal 7.72+ / Drupal 8.8.8+ / Drupal 8.9.1+ / Drupal 9.0.1+ (upgrade to the latest stable release in your major version branch)

  1. 1. Back up your Drupal database and files before proceeding with any upgrade.
  2. 2. Review your current Drupal version by navigating to /admin/reports/status in your Drupal site.
  3. 3. For Drupal 7.x sites: Upgrade to Drupal 7.72 or later.
  4. 4. For Drupal 8.8.x sites: Upgrade to Drupal 8.8.8 or later.
  5. 5. For Drupal 8.9.x sites: Upgrade to Drupal 8.9.1 or later.
  6. 6. For Drupal 9.0.x sites: Upgrade to Drupal 9.0.1 or later.
  7. 7. Run database updates after upgrading via update.php or drush updatedb.
  8. 8. Clear all Drupal caches after the upgrade using drush cr or through the admin interface.
Caveat Major version upgrades (e.g., Drupal 7 to 8/9) may require significant code and theme modifications; always test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drupal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13663 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data