Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Drupal site using vulnerable module
-
ExploitRequest unpublished node URL/ID directly
-
ExecutionAuthorization check bypassed (forceful browsing)
-
ImpactRead unpublished content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target must be a Drupal site running the contributed Unpublished Node Permissions module at a version at or below 1.8.0, and must contain unpublished nodes worth disclosing. The authorization flaw allows directly requesting an unpublished node's URL/ID to bypass the intended access restriction (forceful browsing), so the practical prerequisite is knowing or enumerating the node path. Limiting factors: impact is confined to confidentiality of unpublished content (no modification or denial of service), exposure requires this specific non-core module to be installed and enabled, and the value of the disclosure depends on what unpublished content exists on the site. |
| Impact | This is a moderate-severity information-disclosure issue, not an urgent emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3) indicates a network-reachable, low-complexity flaw needing no privileges or user interaction, but with only a Low confidentiality impact and no integrity or availability impact - consistent with CWE-863 Incorrect Authorization enabling forceful browsing to content that should be hidden. Exploitation signals are weak: EPSS is 0.14% (3rd percentile), there is no CISA KEV listing (not confirmed actively exploited), and no public exploit identified at time of analysis - only a vendor security advisory reference. The vuln.today decision label is 'this_month' rather than act_now/emergency, aligning with the low EPSS and absence of active exploitation. The main real-world mitigant is scope: this is a Drupal contributed module, not Drupal core, so exposure is confined to sites that specifically install the Unpublished Node Permissions module. Net: a legitimate but low-priority confidentiality fix to schedule within normal patch cycles, driven by severity rather than by any evidence of exploitation. |
| Exploit ScenarioDerived | An attacker who knows or guesses the URL/node ID of an unpublished Drupal node directly requests it and the Unpublished Node Permissions authorization check fails to block access, disclosing content intended to remain hidden. No authentication, special tooling, or user interaction is required against a site running the vulnerable module. No public exploit code or PoC reference is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
Forceful browsing in the Drupal contributed module Unpublished Node Permissions (versions 0.0.0 through 1.8.0) lets unauthenticated remote visitors retrieve unpublished node content by requesting a node's URL or ID directly, bypassing the access restriction the module is meant to enforce. Only Drupal sites that have installed and enabled this non-core module are exposed, and the impact is confined to confidentiality of unpublished content, with no modification or denial of service. No public exploit identified at time of analysis; EPSS is 0.14% (3rd percentile) and a vendor patch is available per the Drupal security advisory, so this is a moderate-severity information-disclosure issue to be scheduled for patching this month rather than an emergency.
RemediationAI
Patch available per vendor advisory: update the Unpublished Node Permissions module to the release identified in Drupal security advisory SA-CONTRIB-2026-132 (https://www.drupal.org/sa-contrib-2026-132), which addresses the affected 0.0.0-1.8.0 range; the supplied data does not state the exact fixed version number beyond that affected range, so confirm it on the advisory page before upgrading. Until the update is applied, the most direct compensating control is to disable the module, which removes the exposure but also removes the ability it provides for designated roles to view unpublished nodes; sites that cannot disable it should avoid leaving sensitive material in unpublished nodes, since node paths are enumerable and the disclosure depends entirely on what unpublished content exists. Reviewing unpublished content for credentials, personal data, or pre-publication material and unpublishing or relocating it limits the value of any bypass while the upgrade is pending.
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
Drupal's node access subsystem decides whether a given user may view a node, and contributed modules hook into that system to add grants beyond Drupal core's defaults. Unpublished Node Permissions exists to let site builders grant selected roles the ability to view unpublished nodes, which core does not do by default. The reported weakness is CWE-863 (Incorrect Authorization): the module's access check is not applied consistently, so a request that addresses an unpublished node directly - classic forceful browsing, where the attacker guesses or enumerates the node path instead of following links - is served content that should have been denied. Drupal's routing means node paths are frequently sequential (/node/1, /node/2), making enumeration practical, although the specific code path in which the grant logic fails is not described in the available sources. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) confirms the flaw is remotely reachable without credentials, requires no user interaction, and stays within the vulnerable component, with only low confidentiality impact. The CPE cpe:2.3:a:drupal:unpublished_node_permissions:*:*:*:*:*:*:*:* identifies the affected package as the contributed module itself rather than Drupal core.
Know when Unpublished Node 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:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-reachable forceful browsing with no auth or interaction (AV:N/AC:L/PR:N/UI:N); only unpublished content is disclosed, so C:L with I:N/A:N.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
2DescriptionCVE.org
Incorrect Authorization vulnerability in Drupal Unpublished Node Permissions allows Forceful Browsing. This issue affects Unpublished Node Permissions versions: from 0.0.0 to 1.8.0.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-107867
GHSA-gccc-p56f-qc53
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB