Field Permissions
2 security fixes in one update. Field Permissions fixed 2 separate security bugs at once: 2 access bypass. One update covers all of them. The most serious, SA-CONTRIB-2026-289, is explained here and the full list is at the end of the card.
The module does not properly hide private fields on items that do not have an author. Anyone could see these private fields. They could not change any data.
- Who could do thisAnyone visiting the site. No login needed.
- Does it apply to youAn administrator has set a field to private on an item type that has no author and the attacker can already view that item.
- Has it been used in attacksNo sign of it.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate Field Permissions to 8.x-1.6.
For developers: what the fix changed
The fix updates the PrivateAccess plugin to return FALSE instead of TRUE when an entity lacks an owner. This ensures private fields on these entities are denied access by default.
Also in this release The release also updates the administrator role check to use the isAdmin flag and updates the README.
README.md+3 −1src/FieldPermissionsService.php+22 −2src/Plugin/FieldPermissionType/PrivateAccess.php+5 −1 fix
- Moderately critical · Access bypass · SA-CONTRIB-2026-289
- Moderately critical · Access bypass · SA-CONTRIB-2026-288