Skip to content
Fencer Vulns
medium 6.5

CVE-2022-25270 json

Incorrect authorization in Drupal core

published 2022-02-16 4 y ago modified 2026-09-19 50 d ago also BIT-drupal-2022-25270 , DRUPAL-CORE-2022-004 , EUVD-2022-0877 , GHSA-73q4-j324-2qcc

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

Summary

The Quick Edit module does not properly check entity access in some circumstances. This could result in users with the "access in-place editing" permission viewing some content they are are not authorized to access. Sites are only affected if the QuickEdit module (which comes with the Standard profile) is installed.

Patch / fix

  • packagist drupal/core 9.2.13, 9.3.6
  • bitnami drupal 9.2.13, 9.3.6
  • Drupal Core 9.2.13, 9.3.6

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-2022-25270 updated cvss 5.3

drupal: information disclosure vulnerbility found in drupal core

  • 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist drupal/core
>=9.3.0, <9.3.6
>=8.0.0, <9.2.13
9.3.6
9.2.13
bitnami drupal
>=9.2.0, <9.2.13
>=9.3.0, <9.3.6
9.2.13
9.3.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.