Drupal Field Collection · Improper Authorization Vulnerability
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 31 Oct 2026, 01:39 UTC
Thin evidence
One scorer or none| CNA (drupal) | CVSS 4.0 | 5.3 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DrupalField Collection for Drupal 7 | Affected
| Fixed in– |
AI-suggested
The vulnerability is fixed by requiring users to have access to the parent entity in addition to the "edit field collections" permission before allowing edits or deletions of field collection items. Users should upgrade the Field Collection module to a version later than 7.x-1.2 once available.
Description
An improper authorization vulnerability in the Drupal Field Collection module for Drupal 7 allows users with the "edit field collections" permission to bypass access controls on the parent entity. This flaw permits such users to edit or delete field collection items attached to entities they normally cannot edit. The issue affects versions 7.x-1.0 through 7.x-1.2 of the module.