DRUPAL-CORE-2021-009 BIT-drupal-2020-13676 CVE-2020-13676 GHSA-qfhg-m6r8-xxpj

Incorrect Authorization in Drupal core

Medium Packagist

Severity: 6.5 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 0.80%; Chance of exploitation in the next 30 days. Higher than 56.76% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-284 Improper Access Control; CWE-863 Incorrect Authorization
Fix: 9.2.6; Upgrade drupal/core to this version or later

Description

The QuickEdit module does not properly check access to fields in some circumstances, which can lead to unintended disclosure of field data.

Sites are only affected if the QuickEdit module (which comes with the Standard profile) is installed.

This advisory is not covered by Drupal Steward.

Affected versions

Packagist

Package	Vulnerable	Fixed in
drupal/core	`>= 8.0.0, < 8.9.19` `>= 9.1.0, < 9.1.13` `>= 9.2.0, < 9.2.6`	`8.9.19` `9.1.13` `9.2.6`
drupal/core	`>= 8.0.0, < 8.9.19`	`8.9.19`
drupal/core	`>= 9.1.0, < 9.1.13`	`9.1.13`
drupal/core	`>= 9.2.0, < 9.2.6`	`9.2.6`

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.2.6`

composer

composer require drupal/core:^9.2.6

Severity breakdown

CVSS 3.1 6.5

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

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

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it

Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

CWE-863: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How to prevent it

Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
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. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Advisories

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

Packages

github.com/drupal/core

Timeline

Sep 15, 2021 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: Greg Watson

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