Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability requires authenticated access (PR:L per the description stating 'authenticated users'), reducing the attack surface compared to unauthenticated exploits. The CVSS score and vector data are unavailable in the provided intelligence, preventing formal risk quantification; however, the CWE-200 classification and the impact on access control bypass indicate moderate to significant real-world risk. The exploitation mechanism depends on filename-collision conditions and the presence of hook_node_insert() consumers in the target environment, which introduces some complexity into exploitation. No EPSS score, KEV status, or public exploit code is documented in available sources, suggesting this is not yet actively exploited at scale or widely weaponized. The risk is highest in Drupal environments where File (Field) Paths is actively used in conjunction with email attachment modules or other sensitive file-handling integrations. Organizations running versions prior to 7.1.3 should prioritize patching to eliminate the vulnerability, but the requirement for authentication and the specific configuration dependencies limit the immediate urgency compared to unauthenticated remote code execution flaws. |
| Exploit ScenarioDerived | An authenticated attacker creates a user account on a Drupal 7.x site running File (Field) Paths prior to 7.1.3. The attacker uploads a file with a specific filename designed to collide with a filename recently uploaded by another user to a private file directory. Due to the file URI collision vulnerability, when a hook_node_insert() consumer (such as an email notification module) processes the node creation, it receives and processes the incorrect file URI pointing to the target user's private file instead of the attacker's file. If the email module attaches files based on URI without re-validating access permissions, the private file is disclosed or attached to an email, exposing sensitive information such as confidential documents or personal data that should only be accessible to the file owner. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
Drupal File (Field) Paths module 7.x prior to 7.1.3 allows authenticated users to disclose other users' private files through filename-collision uploads that manipulate file URI processing, causing hook_node_insert() consumers such as email attachment modules to access incorrect file URIs and bypass access controls on sensitive files. The vulnerability affects the Drupal File (Field) Paths package as confirmed via CPE cpe:2.3:a:drupal:drupal_file_(field)_paths:*:*:*:*:*:*:*:*. No public exploit code or active exploitation data has been identified at the time of analysis.
RemediationAI
Upgrade Drupal File (Field) Paths to version 7.1.3 or later immediately. Consult the official Drupal security advisory and the Tag1 Consulting security advisory (https://d7es.tag1.com/security-advisories/file-field-paths-moderately-critical-file-path-manipulation) for detailed patching instructions specific to your Drupal 7.x deployment. As an interim mitigation pending patch deployment, restrict file upload permissions to trusted user roles only and audit any hook_node_insert() implementations or email attachment modules for additional access control validation to ensure they verify file ownership before processing URIs. Monitor file upload logs for suspicious filename-collision patterns or rapid successive uploads from different users with identical filenames.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Drupal File (Field) Paths is a module that manages file field path generation and URI processing for Drupal 7.x installations. The vulnerability exists in the file URI processing logic when handling field paths, specifically in how the module resolves and assigns file URIs during node insertion operations. The root cause is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), indicating insufficient access control validation when processing file paths. The vulnerability exploits a filename-collision condition where two authenticated users uploading files with identical or specially-crafted names can trigger URI assignment confusion, causing the system to associate the wrong file URI with a given file operation. This is particularly dangerous because hook_node_insert() implementations-common in email attachment and file processing modules-consume the potentially incorrect file URI without re-validating access permissions against the private file's actual owner.
Know when Drupal File Field Paths 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
Information disclosure in the file URI processing of File (Field) Paths in Drupal File (Field) Paths 7.x prior to 7.1.3 on Drupal 7.x allows authenticated users to disclose other users’ private files via filename‑collision uploads. This can cause hook_node_insert() consumers (for example, email attachment modules) to receive the wrong file URI, bypassing normal access controls on private files.
Executive ViewAI
CVE-2026-1556 presents notable security risk, a information exposure vulnerability rated CVSS 6.9. Sensitive information could be exposed to unauthorized parties. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict endpoint access, redact sensitive data in logs.
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-16422
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB