Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Drupal site with Node View Permissions installed
-
DeliveryEnumerate or guess restricted node URLs
-
ExploitCraft HTTP request triggering exceptional permission-check condition
-
ExecutionBypass node view access control
-
ImpactRead restricted node content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Unusual condition handling
|
| Exploitation Conditions | The Node View Permissions module must be installed and actively used to restrict access to one or more nodes on the Drupal site. Exploitation requires the attacker to satisfy the high attack complexity condition (AC:H per CVSS vector), meaning a specific exceptional state in the permission check must be triggered - the exact configuration trigger is not detailed in the available advisory text and should be confirmed via the Drupal security advisory at https://www.drupal.org/sa-contrib-2026-034. No authentication is required (PR:N per CVSS vector) and no user interaction is needed (UI:N). Exploitation is limited to reading node content (confidentiality only); attackers cannot modify data or cause service disruption. Sites that do not use the Node View Permissions module are not affected. |
| Impact | The composite risk profile for this vulnerability is low. CVSS 3.7 is corroborated by all available signals: AV:N confirms reachability over the network, but AC:H limits exploitability to scenarios where specific preconditions are met, substantially reducing the attack surface. PR:N means no authentication is required, but the high complexity partially offsets this advantage for an attacker. Impact is limited to confidentiality (C:L) with no integrity or availability consequence (I:N/A:N) and no scope change (S:U). EPSS at 0.01% (3rd percentile) strongly indicates this vulnerability is not being actively targeted or easily reproduced at scale. The absence from CISA KEV and the absence of any identified POC further support treating this as a routine patch-cycle issue rather than an emergency. No conflicting signals were identified between CVSS and the description - the high-complexity network vector is consistent with a conditional forceful browsing flaw. |
| Exploit ScenarioDerived | An attacker identifies a Drupal site with Node View Permissions installed and discovers or enumerates node IDs (e.g., /node/42) for content that should be access-restricted. By crafting a direct HTTP request that triggers an edge-case condition in the module's permission evaluation logic, the attacker receives the restricted node content without authentication. The high attack complexity (AC:H) implies the attacker must identify and satisfy a specific precondition - such as a particular node configuration or request state - before the bypass succeeds. No public POC has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 20, 2026
Forceful browsing in the Drupal Node View Permissions module exposes restricted node content to unauthenticated network attackers under high-complexity conditions. Affected are all installations running versions 0.0.0-1.7.0 (branch 1.x) and 2.0.0-2.0.1 (branch 2.x) of the module. The vulnerability is classified as information disclosure only - no integrity or availability impact - and carries a CVSS 3.7 (Low) score; no public exploit code exists and no confirmed active exploitation has been reported (not in CISA KEV), with EPSS placing exploitation probability at 0.01%.
RemediationAI
Sites running the 1.x branch should upgrade to Node View Permissions 1.7.0; sites running the 2.x branch should upgrade to 2.0.1. Both patched versions are confirmed available per the Drupal security advisory at https://www.drupal.org/sa-contrib-2026-034. Upgrading via Composer (composer update drupal/node_view_permissions) is the recommended approach on modern Drupal installations. If an immediate upgrade is not feasible, a compensating control is to disable the Node View Permissions module entirely and rely on Drupal core's built-in content access controls - note this trade-off removes the granular per-node view restrictions the module provides. Given the low CVSS score and high attack complexity, this vulnerability can be addressed within a normal patch maintenance window rather than requiring emergency remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Node View Permissions module (cpe:2.3:a:drupal:node_view_permissions) extends Drupal's content access control by restricting which roles can view specific nodes. CWE-754 (Improper Check for Unusual or Exceptional Conditions) indicates the root cause is a logic gap: the module fails to correctly handle edge-case or exceptional states during permission evaluation, leaving certain code paths unchecked. This maps to a forceful browsing weakness - an attacker can directly request node URLs and receive content that access control rules should have blocked, because the exceptional condition that should trigger a deny is not caught. The flaw exists across two independent version branches (1.x and 2.x), suggesting the logic error is present in shared permission-checking code rather than a branch-specific change.
Know when Node View Permissions gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Primary rating from Vendor (drupal) · only source for this CVE.
CVSS VectorVendor: drupal
Lifecycle Timeline
3DescriptionCVE.org
Improper Check for Unusual or Exceptional Conditions vulnerability in Drupal Node View Permissions allows Forceful Browsing.
This issue affects Node View Permissions: from 0.0.0 before 1.7.0, from 2.0.0 before 2.0.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-30991
GHSA-xrm3-543w-4g3q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB