dbcve.org
DrupalCMS

CVE-2022-25274

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-26
Fix available
A fix is available. Upgrade to 9.3.12 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Drupal 9.3 implemented a generic entity access API for entity revisions. However, this API was not completely integrated with existing permissions, resulting in some possible access bypass for users who have access to use revisions of content generally, but who do not have access to individual items of node and media content. This vulnerability only affects sites using Drupal's revision system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Drupal 9.3 introduced a generic entity access API for entity revisions that was not fully integrated with existing permission checks, allowing users with revision access but without individual item access to potentially bypass access controls for node and media content revisions.

MitigationSites using Drupal's revision system should update to a patched version of Drupal core that properly integrates the entity access API with existing permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DrupalCMS
Affected:>= 9.3.0, < 9.3.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Drupal core version
    Run `drush status` or look in `core/lib/Drupal.php` for the VERSION constant, or check `composer.lock` for drupal/core version
    Affected if Version is 9.3.0 through 9.3.11 (anything < 9.3.12 while >= 9.3.0)
  2. Verify node revision module is enabled
    Run `drush pm-list --status=enabled | grep node` or check the Drupal admin UI at /admin/modules for the Content Moderation module or Node Revision functionality
    Affected if Node revision system or Content Moderation module is enabled
  3. Verify media revision support is in use
    Run `drush field-info fields --entity-type=media` or check if any media types have revisions enabled in /admin/structure/media or via config export
    Affected if Media entities are configured with revision support enabled
  4. Check for custom permission bypass scenarios
    Review user roles that have 'view own unpublished content' or 'view revisions' permissions but lack 'view any X content' permissions; check if any role can access /node/{node}/revisions/{revision_id}/view without owning the content
    Affected if Users have revision access permissions without corresponding content view permissions

You are affected if running Drupal core 9.3.0-9.3.11 AND using the revision system for nodes or media, where users may have revision-level permissions without full content access rights.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.3.12 or later
Fixed in 9.3.12
Interim mitigation

Sites using Drupal's revision system should update to a patched version of Drupal core that properly integrates the entity access API with existing permissions.

Recommended fix High confidence

9.3.12

  1. Back up the Drupal database and files
  2. Run `composer require drupal/core:^9.3.12 --no-update` to specify the fixed version
  3. Run `composer update drupal/core --with-all-dependencies` to install the updated core
  4. Run database updates using `drush updatedb` or `php core/scripts/drupal.php updatedb`
  5. Clear the Drupal cache using `drush cr` or `php core/scripts/drupal.php cache-clear`

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drupal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25274 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data