Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Drupal JSON:API endpoint
-
ExploitRequest role-restricted resource directly
-
ExecutionAuthorization check incorrectly passes
-
ImpactRead/alter restricted entity data
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 | Requires the target Drupal site to have the third-party Jsonapi Role Access contrib module installed and enabled at a version from 0.0.0 up to (but not including) 2.0.2, with Drupal's JSON:API functionality active, since the module's purpose is to gate JSON:API resource access by role. Because CVSS is AV:N/AC:L/PR:N/UI:N, no authentication or user interaction is needed once that module is present, and exploitation works against affected default installs of the module. The principal limiting factor is deployment scope - only sites that have chosen to install this specific contrib module are affected, and impact is bounded to low confidentiality and low integrity (no availability effect); the specific request that triggers the authorization failure is not detailed in the available sources. |
| Impact | This is a moderate-severity authorization flaw, not an urgent one. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated issue, which is why it lands at 6.5; however, impact is capped at C:L/I:L/A:N, so no full data compromise, no integrity destruction, and no availability loss are indicated. The exploitation-probability signals all point low-to-moderate: EPSS is only 0.14% (3rd percentile), there is no CISA KEV listing (not actively exploited), and no public exploit identified at time of analysis. The vuln.today decision label is 'this_month' rather than act_now or emergency, and no SSVC automatable/technical-impact fields were supplied to refine this further. Net: a legitimate patch-worthy authorization bypass that exposes role-restricted JSON:API data, but current evidence indicates targeted/opportunistic rather than widespread exploitation. One caveat: the input Tags label this 'Authentication Bypass' while the CWE-863 classification and 'Forceful Browsing' description make it an authorization (not authentication) flaw - treat it as improper access control over JSON:API resources, not a credential bypass. |
| Exploit ScenarioDerived | An unauthenticated remote attacker directly requests JSON:API resource endpoints on a Drupal site running the Jsonapi Role Access module (version below 2.0.2) and, due to incorrect authorization, retrieves or modifies entity data that should have been restricted to specific roles. No public exploit code has been identified, and the precise request pattern that triggers the bypass is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
Unauthenticated forceful browsing in the Drupal contrib module Jsonapi Role Access allows remote attackers to reach JSON:API resources that the module is supposed to restrict by role, with low confidentiality and low integrity impact and no availability effect. Sites are affected only if they run this specific contrib module at a version below the fixed release and have Drupal's JSON:API functionality active; the CVSS vector (AV:N/AC:L/PR:N/UI:N) means no credentials or user interaction are needed once the module is present. Severity is moderate (6.5) and urgency is limited: EPSS is 0.14% (3rd percentile), there is no KEV entry, and no public exploit identified at time of analysis; a vendor patch is available and the priority label is this_month.
RemediationAI
Vendor-released patch available: update the Jsonapi Role Access contrib module to the fixed release and confirm the exact version boundary in the Drupal advisory https://www.drupal.org/sa-contrib-2026-127, since the CVE description lists the affected range as 0.0.0 to 2.0.2 while EUVD records it as 0.0.0 <2.0.2 and therefore treats 2.0.2 as the fix; sites on 2.0.2 should verify against the advisory rather than assume they are patched. Prioritize remediation on any site where the module is actually enabled alongside JSON:API and where the resource gating matters for data exposure, then inventory other Drupal installs to confirm whether the module is present at all, since unaffected sites need no action. Drupal contrib module updates are typically applied by replacing the module code via Composer or the update workflow and running the database update step; validate the JSON:API permission behavior for each role after upgrading. The available sources do not document a vendor-supported workaround beyond updating, so interim compensating measures (for example removing the module, or restricting the /jsonapi path at the web server or reverse proxy) should be evaluated with their trade-offs in mind: disabling the module removes its role-based gating entirely and leaves access governed by Drupal core JSON:API permissions, and path-level blocking can break legitimate JSON:API consumers such as decoupled front ends.
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 flaw is CWE-863 (Incorrect Authorization) in a third-party Drupal contrib module whose entire purpose is to gate JSON:API resource exposure according to the requesting user's roles. Drupal's JSON:API (core) serves entity resources over HTTP under the /jsonapi path space, and this module layers per-role access control on top of that routing; the authorization check performed by the module can be bypassed, which the Drupal security team classifies as forceful browsing - requesting endpoints or resources directly rather than through the intended access-controlled flow. The affected package is identified as cpe:2.3:a:drupal:jsonapi_role_access. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, the bypass is reachable over the network without authentication and without user interaction; impact is scored C:L/I:L/A:N. The specific request, route, or code path that triggers the authorization failure is not described in the available sources, and no root-cause detail beyond the CWE classification is provided.
Know when Jsonapi Role Access 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:L/A:N
Forceful browsing of JSON:API over the network needs no auth or interaction (AV:N/AC:L/PR:N/UI:N); unauthorized read and limited write map to C:L/I:L, with no availability impact and unchanged scope.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
3DescriptionCVE.org
Incorrect Authorization vulnerability in Drupal Jsonapi Role Access allows Forceful Browsing. This issue affects Jsonapi Role Access versions: from 0.0.0 to 2.0.2.
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-107872
GHSA-c7pp-2r5r-f6pc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB