Skip to content
Fencer Vulns
high 7.5

CVE-2020-13677 json

Drupal core access bypass vulnerability

published 2021-09-15 5 y ago modified 2026-09-19 50 d ago also BIT-drupal-2020-13677 , DRUPAL-CORE-2021-010 , EUVD-2022-0799 , GHSA-3xr3-phjp-g6p2

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

Under some circumstances, the Drupal core JSON:API module does not properly restrict access to certain content, which may result in unintended access bypass. Sites that do not have the JSON:API module enabled are not affected.

Patch / fix

  • packagist drupal/core 8.9.19, 9.1.13, 9.2.6
  • bitnami drupal 8.9.19, 9.1.13, 9.2.6
  • Drupal Core 8.9.19, 9.1.13, 9.2.6
  • drupal Arch Linux 9.2.6-1

arch linux advisories AVG-2407

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-13677 updated

drupal: multiple vulnerabiltiies

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist 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
bitnami drupal
>=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

Affected products

  • Drupal Core

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.