# CVE-2020-13674: Cross-Site Request Forgery in Drupal core

> Attackers can exploit CSRF in the QuickEdit module to modify data integrity if the module is installed.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-drupal-2020-13674, DRUPAL-CORE-2021-007, GHSA-j586-cj67-vg4p

## What is CVE-2020-13674?

CVE-2020-13674 is a medium-severity vulnerability in Drupal Drupal, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The QuickEdit module does not properly validate access to routes, which could allow cross-site request forgery under some circumstances and lead to possible data integrity issues. Sites are only affected if the QuickEdit module (which comes with the Standard profile) is installed. Removing the "access in-place editing" permission from untrusted users will not fully mitigate the vulnerability.

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

## Which versions are affected by CVE-2020-13674?

8 open source packages ship an affected version, including drupal/core and drupal. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 8.0.0 | 8.9.19, 9.1.13, 9.2.6 |
| `drupal/core` | Packagist | From 8.0.0 | 8.9.19 |
| `drupal/core` | Packagist | From 8.0.0 | 8.9.19 |
| `drupal/core` | Packagist | From 9.1.0 | 9.1.13 |
| `drupal/core` | Packagist | From 9.1.0 | 9.1.13 |
| `drupal/core` | Packagist | From 9.2.0 | 9.2.6 |
| `drupal/core` | Packagist | From 9.2.0 | 9.2.6 |
| `drupal` | Bitnami | From 8.9.0 | 8.9.19, 9.1.13, 9.2.6 |

Products: Drupal Drupal.

## How do I fix CVE-2020-13674?

Upgrade drupal/core to a fixed version for your release line: 8.9.19, 9.1.13 or 9.2.6.

## Is CVE-2020-13674 being exploited?

There is no known exploitation of CVE-2020-13674 in the wild and no public exploit code.

## Other vulnerabilities in Drupal Drupal

- [CVE-2026-9082](https://insights.sbomify.com/CVE-2026-9082/): Drupal Core SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-13671](https://insights.sbomify.com/CVE-2020-13671/): Drupal core Un-restricted Upload of File (high 8.8, exploited in the wild)
- [CVE-2019-6340](https://insights.sbomify.com/CVE-2019-6340/): Drupal Core Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2009-3352](https://insights.sbomify.com/CVE-2009-3352/): Other in n/a (critical 10.0)
- [CVE-2024-55636](https://insights.sbomify.com/CVE-2024-55636/): Drupal core - Less critical - Gadget chain - SA-CORE-2024-006 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13674 and fix it if it is affected.

What it is: CVE-2020-13674 is a medium-severity vulnerability in Drupal Drupal, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-13674 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.9.19, 9.1.13, 9.2.6
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.9.19
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.9.19
- drupal/core (Packagist): affected from 9.1.0; fixed in 9.1.13
- drupal/core (Packagist): affected from 9.1.0; fixed in 9.1.13
- drupal/core (Packagist): affected from 9.2.0; fixed in 9.2.6
- drupal/core (Packagist): affected from 9.2.0; fixed in 9.2.6
- drupal (Bitnami): affected from 8.9.0; fixed in 8.9.19, 9.1.13, 9.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-13674/ (Markdown: https://insights.sbomify.com/CVE-2020-13674/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13674
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13674
- OSV: https://osv.dev/vulnerability/CVE-2020-13674

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-13674/
Summaries are generated and may contain mistakes; the official description above is the record.