Field Collection for Drupal 7 access bypass via missing parent entity access check
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in NES 7.1.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Field Collection module for Drupal 7 is affected. A user who has the "edit field collections" permission can edit or delete field collection items attached to content they are not otherwise allowed to modify, bypassing the access restrictions on the parent entity.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Improper Authorization vulnerability in Drupal Field Collection for Drupal 7 allows a user with the "edit field collections" permission to bypass access control on the parent (host) entity. The access check for field collection items (field_collection_item_access()) granted edit and delete access to any user holding the "edit field collections" permission without verifying the user's access to the host entity. As a result, a user with "edit field collections" but without edit/update access to the host entity (for example a node they cannot edit) could edit or delete field collection items attached to that entity, bypassing the intended entity/node access restrictions. The fix requires access to the parent entity in addition to the field collection permission. This issue affects Field Collection for Drupal 7: version 7.x-1.0 up to and including 7.x-1.2.
Timeline
- CVE published1 day
- First seen by cve.now
Affected versions
- Drupal Field Collection for Drupal 7
From 7.x-1.0 · through 7.x-1.2
References 2
herodevs.com
d7es.tag1.com
Questions about CVE-2026-77152
What does this mean?
Users with the "edit field collections" permission can edit or delete field collection items attached to host entities such as nodes. Node and entity access controls that should block those changes are bypassed because the parent entity access check is missing.Source: herodevs.com
Am I affected, and how do I check?
The product range listed is Field Collection for Drupal 7 from 7.x-1.0 through 7.x-1.2, and the advisory also names module version 7.1.0 as affected. To check a site, look at the installed Field Collection module version on the modules page and see whether any users hold the "edit field collections" permission.Source: herodevs.com
What should I do about it?
Upgrade Field Collection to NES 7.1.3, which is the fixed version. Until the upgrade is done, restrict the "edit field collections" permission to highly trusted users only.Source: herodevs.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data