dbcve.org
Quick Node BlockDrupal extension · Quick Node Block Project

CVE-2025-48013

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 Authorization vulnerability in Drupal Quick Node Block allows Forceful Browsing.This issue affects Quick Node Block: from 0.0.0 before 2.0.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 · high confidence

Missing authorization in Drupal Quick Node Block module allows forceful browsing, enabling unauthenticated or low-privileged users to access content or pages that should require proper authentication or elevated permissions. This affects all versions prior to 2.0.0.

MitigationUpgrade to Quick Node Block version 2.0.0 or later which includes proper authorization controls. If immediate patching is not possible, review and restrict access to the affected module's paths via Drupal's role permissions or web server configuration.

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
Quick Node BlockDrupal extension
Affected:= 2.0.x

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 if Quick Node Block module is installed
    Check for the presence of the module directory at /modules/contrib/quick_node_block/ or list installed modules via Drush: drush pm-list --type=module --status=enabled | grep -i quick_node_block
    Affected if The module is present and enabled in the Drupal installation
  2. Determine the installed version of Quick Node Block
    Review the composer.json file in the Drupal root for 'drupal/quick_node_block' entry under 'require', or inspect the module's .info.yml file located at modules/contrib/quick_node_block/quick_node_block.info.yml for the 'version' field
    Affected if The version listed is earlier than 2.0.0 (for example, 1.x versions)
  3. Verify access controls on module paths
    Test accessing Quick Node Block administrative paths without authentication or with a low-privileged user account (such as an authenticated user with no admin roles). Attempt to access node block configuration or content creation pages provided by the module
    Affected if Unauthenticated or low-privileged users can access pages or create/modify node blocks that should require elevated permissions
  4. Check Drupal role permissions for Quick Node Block
    Navigate to /admin/people/permissions (or Administration > People > Permissions) and examine if permissions for 'Quick Node Block' are incorrectly granted to anonymous or low-privileged roles
    Affected if The module grants access permissions to Anonymous User or Authenticated User roles for administrative or privileged operations

A user is affected if Quick Node Block module version is earlier than 2.0.0 AND the module is installed and accessible to unauthenticated or low-privileged users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Quick Node Block version 2.0.0 or later which includes proper authorization controls. If immediate patching is not possible, review and restrict access to the affected module's paths via Drupal's role permissions or web server configuration.

Recommended fix Moderate confidence

2.0.0 or later

  1. 1. Back up your Drupal site database and files.
  2. 2. Update the Quick Node Block module to version 2.0.0 or later using Composer: `composer update drupal/quick_node_block --with-all-dependencies`
  3. 3. Clear Drupal caches: `drush cr` or via the admin UI at Admin > Configuration > Development > Performance > Clear all caches.
  4. 4. Verify the update was successful by checking the module version at Admin > Extend > Quick Node Block.

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

Fix this in Quick Node Block Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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