dbcve.org
PanelsDrupal extension · Drupal

CVE-2025-3474

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 4.9 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authentication for Critical Function vulnerability in Drupal Panels allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Panels: from 0.0.0 before 4.9.0.

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 · moderate confidence

The Drupal Panels module versions before 4.9.0 contain a missing authentication vulnerability for a critical function, allowing unauthenticated attackers to exploit incorrectly configured access control security levels. This enables unauthorized access to panel management functions that should require authentication.

MitigationUpgrade Drupal Panels to version 4.9.0 or later to obtain the authentication fix. Review and verify all panel access control configurations are properly set after upgrading.

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
PanelsDrupal extension
Affected:< 4.9

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Drupal Panels version
    Check the modules/panels directory or Drupal admin interface at /admin/modules for the Panels module version number
    Affected if The installed version is any version prior to 4.9.0
  2. Verify panel access control configuration
    Review the access control settings for panel pages and variants in the Drupal Panels UI at /admin/structure/panels or via drush panopoly:list
    Affected if Any panel page or variant has access control set to allow unauthenticated (anonymous) users
  3. Test unauthenticated panel management access
    Attempt to access panel management routes such as panel editing, variant addition, or panel preview pages without providing authentication credentials
    Affected if The system allows unauthenticated access to any panel management or editing functions
  4. Inspect panel configuration files
    Check the panel configuration stored in the Drupal database (config table) or exported configuration files for access settings on panel entities
    Affected if Any panel configuration shows 'access' or 'logic' settings that grant permission to anonymous user roles

A user is affected if their Drupal Panels module version is below 4.9.0 AND any panel access control is configured to permit unauthenticated users, allowing unauthorized panel management access.

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 4.9 or later
Fixed in 4.9
Interim mitigation

Upgrade Drupal Panels to version 4.9.0 or later to obtain the authentication fix. Review and verify all panel access control configurations are properly set after upgrading.

Recommended fix High confidence

4.9.0

  1. 1. Backup your Drupal database and files before making any changes.
  2. 2. Update the Panels module to version 4.9.0 or later using Composer: `composer update drupal/panels` or via the Drupal admin interface.
  3. 3. Clear the Drupal cache after upgrading: `drush cr` or via Admin > Configuration > Development > Performance > Clear all caches.
  4. 4. Verify the upgrade was successful by checking the Panels module version at Admin > Structure > Panels (or the module administration page).

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

Fix this in Panels Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3474 — 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-2025-3474 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