Forum Access
The module fails to prevent users from starting new discussions in areas where they should only be able to read. An ordinary account on the site could add new content to a private area. They would not be able to view any hidden information.
- Who could do thisOnly someone with a login on your site.
- Does it apply to youSites are affected if the discussion area does not use the default selection tool or if content is created through a web services data feed.
- 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 Forum Access to 2.0.3.
For developers: what the fix changed
The fix introduces a new validation constraint, `ForumAccessCreate`, and attaches it to the `taxonomy_forums` field via `forum_access_entity_bundle_field_info_alter()` in `forum_access.module`. The constraint validator in `ForumCreateAccessConstraintValidator.php` enforces the 'create' grant on the forum, ensuring access checks apply to all input methods including autocomplete widgets and APIs.
Also in this release Added a post-update hook to rebuild caches and updated a test group annotation.
forum_access.module+23 −5 fixforum_access.post_update.php+14 −0includes/forum_access.common.inc+4 −2 fixsrc/Plugin/Validation/Constraint/ForumCreateAccessConstraint.php+32 −0 fixsrc/Plugin/Validation/Constraint/ForumCreateAccessConstraintValidator.php+94 −0 fix