Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Drupal core access bypass vulnerability

CVE-2020-13677GHSA-3xr3-phjp-g6p2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (drupal/core 9.2.6, 9.1.13, 8.9.19), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist drupal/core

    Affected
    >= 8.0.0, < 8.9.19>= 9.1.0, < 9.1.13>= 9.2.0, < 9.2.6
    Fixed in
    8.9.19, 9.2.6, 9.1.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2020-13677: 1.22% estimated exploitation activity in the next 30 days; percentile 68.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-3xr3-phjp-g6p2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-13677

Advisory: Drupal core access bypass vulnerability
IDs: CVE-2020-13677, GHSA-3xr3-phjp-g6p2
Record: https://patchnext.com/advisories/cve-2020-13677 (revision 1, source checked 26 Oct 2026, 14:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: drupal/core 9.2.6, 9.1.13, 8.9.19. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist drupal/core: affected >= 8.0.0, < 8.9.19; >= 9.1.0, < 9.1.13; >= 9.2.0, < 9.2.6; fixed in 8.9.19, 9.2.6, 9.1.13

## Suggested inspection (read-only)
- Packagist drupal/core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on drupal/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3xr3-phjp-g6p2 (GitHub-reviewed advisory GHSA-3xr3-phjp-g6p2 lists affected ranges: Packagist drupal/core >=8.0.0 =9.1.0 =9.2.0 <9.2.6)

Commands are suggestions: review each one before running it.

Loading voting…