Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged Drupal user
-
ExploitRequest restricted Mermaid field URL
-
ExecutionBypass missing authorization check
-
ImpactRead unauthorized diagram 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 | Exploitation requires an installed Drupal site running the Mermaid Diagram Field contrib module at a version between 1.0.4 and 1.0.9, and an attacker who already holds a valid low-privileged account on that site (PR:L). The flaw is an access-control gap allowing such an authenticated user to forcefully browse to Mermaid diagram field content they should not be permitted to see. Limiting factors: authentication is required (not anonymous/remote-unauthenticated), the CVSS vector models required user interaction (UI:R), impact is confined to limited confidentiality disclosure of diagram content (I:N/A:N), and the precise configuration or URL pattern that triggers the bypass is not detailed in the available advisory text. |
| Impact | All available signals point to a low real-world priority. The CVSS 3.1 base score is only 3.5 (LOW), and the vector (AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N) indicates that while the issue is network-reachable with low complexity, it requires an already-authenticated low-privileged account (PR:L) plus user interaction (UI:R), and the only impact is a limited confidentiality exposure (C:L) with no integrity or availability effect. EPSS reinforces this: 0.18% probability at the 7th percentile is very low, and the vulnerability is NOT on the CISA KEV list, so there is no evidence of active exploitation. The vuln.today Decision label is 'monitor', consistent with the low severity and low EPSS. No SSVC fields (automatable, technical impact) were supplied in the input, so that framework cannot be cross-referenced. The signals are therefore internally consistent - a genuine but minor authorization weakness, not a high-CVSS-but-low-risk anomaly and not an urgent threat. One caveat: the 'Authentication Bypass' tag overstates the issue, which is actually incorrect authorization (CWE-863) / forceful browsing, i.e. an authenticated user reaching content they should not, not a bypass of authentication itself. |
| Exploit ScenarioDerived | A low-privileged authenticated Drupal user navigates directly to a Mermaid Diagram Field resource URL that they are not authorized to view, and the module fails to enforce access control (forceful browsing), disclosing the diagram content. No public exploit code was identified in the input; the only references are the Drupal security advisory and the NVD entry. The CVSS vector's AC:L and UI:R indicate the action is simple but is modeled as involving some user interaction; the exact trigger 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
Mermaid Diagram Field 1.0.4 to 1.0.9, a contributed Drupal module, contains an access-control gap (CWE-863) that lets a user who already holds a valid low-privileged account reach Mermaid diagram field content they are not permitted to view by requesting it directly (forceful browsing). The result is limited confidentiality exposure of diagram content only - integrity and availability are unaffected - and the CVSS vector (AV:N/AC:L/PR:L/UI:R, CVSS 3.5) models both an authenticated attacker and a user-interaction component. No public exploit code has been identified at time of analysis, EPSS is 0.18% (7th percentile), and the case is not in CISA KEV; the vuln.today decision label is monitor, consistent with a low real-world priority.
RemediationAI
Patch status is 'Patch available per vendor advisory': the Drupal security team has published a fix, and the exact fixed release is named in the advisory at https://www.drupal.org/sa-contrib-2026-180 - the input data does not enumerate that version number, so confirm it on the advisory before upgrading and move off any 1.0.4-1.0.9 install. Update the contributed module through the normal Drupal module update path (composer update for the module package, then run database updates) and verify the module's reported version afterwards. Because the vulnerability is an authorization bypass rather than something exposed by a network service, no port or endpoint blocking guidance is supplied by the available sources, and the advisory text reviewed does not describe a workaround; where an update cannot be applied promptly, disabling the Mermaid Diagram Field module removes the exposure but will make any existing diagram field content unrenderable until the module is restored. Restricting which roles hold accounts on the site reduces the set of potential attackers (PR:L is required) but does not fix the underlying check, and the specific URL pattern to monitor for forceful-browsing attempts is not documented in the available sources.
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 affected component is a Drupal contributed module that defines a field type for rendering Mermaid diagrams, so content is stored and rendered as field data attached to Drupal entities. The root cause class is CWE-863 (Incorrect Authorization): the module fails to enforce a proper access check, letting an authenticated user bypass the normal permission boundary that should gate viewing of that field content. The classic exposure pattern for this class is forceful browsing - an attacker who is already logged in constructs or guesses a direct path or request to the underlying field content rather than navigating through a UI that would have applied the check. Drupal's own permission model distinguishes 'view' access on fields and content from mere authenticated access, which is why the vector requires PR:L rather than PR:N: the flaw does not grant access to anonymous visitors, it lets a low-privileged account exceed its granted permissions in a narrow way (C:L only). The available advisory text does not describe the exact configuration, route, or URL pattern that triggers the bypass, so the specific request that causes the disclosure is not confirmed from the sources reviewed.
Know when Mermaid Diagram Field 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:L/UI:R/S:U/C:L/I:N/A:N
Authenticated low-privileged user needed (PR:L) over the network (AV:N); forceful browsing yields only limited content disclosure (C:L, I:N, A:N); UI:R retained as published since the trigger is not described.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
2DescriptionCVE.org
Incorrect Authorization vulnerability in Drupal Mermaid Diagram Field allows Forceful Browsing. This issue affects Mermaid Diagram Field versions: from 1.0.4 to 1.0.9.
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-107821
GHSA-h68g-2xqj-xfj8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB